Feature/project wizard next button validation

[sharon-wang]

Intent

• More UI work for Epic: New Project Wizards for Beta #2110

Disable the Next and Create buttons if user input is invalid or missing for a particular step.

Shows the Next/Create buttons in disabled state

proj_wiz_next_button_validation.mp4

proj_name_next.mp4

Shows different theme colours for the button enabled/disabled state

buttons_enabled_disabled_theme.mp4

Approach

• specify the appropriate disable condition for the nextButtonConfig/okButtonConfig on each step
• add some colours for the disabled button styling (foreground, background, border)
• add missing border on the Browse... button for the labeledFolderInput component
• fix some logic around the selected interpreter (check that the preferred/selected interpreter is an option in the dropdown list)

QA Notes

• On the project type step, the Next button should be disabled until the user selects one of the options
• On the project name and location step, the Next button should be disabled if the project name is empty (a future PR will address providing feedback to inform the user that they need to enter a project name)
• On the environment/configuration steps, the Create button should be disabled until a valid Python or R interpreter is selected

Note that the conda python interpreter dropdown items are hardcoded, so none of the options are valid (and thus, the Create button cannot be enabled). Once the conda interpreters are attributed to actual runtimes, we will be able to validate the selected item in the dropdown list.

[petetronic]

Are these null because disabled buttons assume the dialog background for their background?

[sharon-wang]

Yes exactly 👍