You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
The defaulting should only be done after submission phase.
the current validation updated the fields that is empty with default values, should not change users original form.
check all the fields that has this problem and then rank the priority
And we should not change user already specified values in any phase.
scarlett2018
changed the title
P2: The defaulting should only be done after submission phase
The defaulting should only be done after submission phase
May 28, 2020
A new page for users who imports an exact config and directly submit it to api (quick access ui for api), enable user to edit config in an editor and do not add extra change.
If user submit job through wizard, some changes are inevitable. But still not add more properties and leave the null values for job protocol.
the current validation updated the fields that is empty with default values, should not change users original form.
Originally posted by @scarlett2018 in #3823 (comment)
The text was updated successfully, but these errors were encountered: