-
Notifications
You must be signed in to change notification settings - Fork 1
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
Set mandatory constraints #50
Labels
Comments
mattiagiupponi
added a commit
that referenced
this issue
Mar 2, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 2, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 2, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 3, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 4, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 4, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 9, 2021
mattiagiupponi
added a commit
that referenced
this issue
Mar 9, 2021
etj
pushed a commit
that referenced
this issue
Mar 11, 2021
* Task #50: add js for constraints * Task #50: add required style * Task #50: placeholder added * Task #50: placeholder * Task #50: required fields for custom tab * Task #50: merge Add dynamic constraints in UI * Task 50: removed unused variable * Task #50: cleanup debug logs in js * Task #50: align rndt template with master * Task #50: align rndt template with master
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some fields that are optional in the base ISO19115 model, may become mandatory in sub profiles.
We need a way to flag which fields are mandatory.
User should be able to understand which fields are mandatory.
The mandatory/optional indication above the tab name should report if all fields in that tab are mandatory
A validation check should be enforced when saving the metadata.
The text was updated successfully, but these errors were encountered: