-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable entry of bareNumber for Integer data types #110
Labels
env:MacOS
This issue is related to running Data Curator on macOS
env:Windows
This issue is related to running Data Curator on Windows
est:Minor
Minor effort to implement
f:Feature-request
This issue is a request for a new feature
fn:Set-Properties
priority:Medium
Milestone
Comments
Stephen-Gates
added
env:MacOS
This issue is related to running Data Curator on macOS
problem:Bug
A bug
priority:High
labels
Sep 27, 2017
Stephen-Gates
added
the
env:Windows
This issue is related to running Data Curator on Windows
label
Sep 28, 2017
Required when we implement Open Data Package function as the schema may include the bareNumber option |
Stephen-Gates
added
priority:Low
f:Feature-request
This issue is a request for a new feature
and removed
problem:Bug
A bug
priority:Low
labels
Dec 13, 2017
/remind me to draft the user interface and acceptance tests on 18 April |
@Stephen-Gates set a reminder for Apr 18th 2018 |
ui to mirror |
Closed
👋 @Stephen-Gates, draft the user interface and acceptance tests |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
env:MacOS
This issue is related to running Data Curator on macOS
env:Windows
This issue is related to running Data Curator on Windows
est:Minor
Minor effort to implement
f:Feature-request
This issue is a request for a new feature
fn:Set-Properties
priority:Medium
Expected Behaviour
When I choose
integer
as a Type, allow me to enter a boolean value for bareNumberCurrent Behaviour
I cannot enter the bareNumber parameter
Your Environment
The text was updated successfully, but these errors were encountered: