Skip to content
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 #4576

Open
1 of 3 tasks
scarlett2018 opened this issue May 28, 2020 · 2 comments
Open
1 of 3 tasks

The defaulting should only be done after submission phase #4576

scarlett2018 opened this issue May 28, 2020 · 2 comments
Assignees

Comments

@scarlett2018
Copy link
Member

scarlett2018 commented May 28, 2020

  • 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.

Originally posted by @scarlett2018 in #3823 (comment)

@scarlett2018 scarlett2018 added this to the Backlog milestone May 28, 2020
@scarlett2018 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
@scarlett2018 scarlett2018 mentioned this issue Jun 1, 2020
47 tasks
@debuggy
Copy link
Contributor

debuggy commented Jul 2, 2020

solution:

  1. 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.
  2. If user submit job through wizard, some changes are inevitable. But still not add more properties and leave the null values for job protocol.

@yqwang-ms
Copy link
Member

Where is the "new page for users"?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants