-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Creating a new project form #1325
Creating a new project form #1325
Conversation
Want to review this pull request? Take a look at this documentation for a step by step guide! From your project repository, check out a new branch and test the changes.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
Suggest add spacing for layout shift from helperText once we include form validation. Everything else looks good to me :)
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Stakeholder Testing Video: https://drive.google.com/file/d/1KBcMbdwVtjXTlIf3P6j0ecvHSc7i1vWt/viewNotes
Questions
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MattPereira This is awesome! The form matches the Figma design and works great! I approve the changes but wanted to open up some discussion regarding the save/close buttons. I LOVE that you use the save button until all fields are complete, but I noticed that the user can't click the close button at this point. I know it is more likely that the user will click save more often than close but should we still give them the option to close as well?
Regardless, great job on this! 🚀
bd107c9
to
9ac678d
Compare
@plang-psm I definitely welcome discussion of this edge case. I think we should ask for more clarification on the save and close buttons at the next meeting. In the most recent testing video, the figma they are using shows the close button disabled when the save button is enabled so I'm going to leave it as is for now. |
Looking back through this: // client/src/components/ProjectForm.js
// ...
<Typography sx={{ fontSize: '18px', fontWeight: '600' }}>
Project Information
</Typography>
// ... Should probaby have a <Typography varinat="h2" sx={{ fontSize: '18px', fontWeight: '600' }}> |
Fixes #1245
What changes did you make and why did you make them ?
ProjectForm.js
that can hopefully be re-used for editing projects/projects/create
that the "Add a New Project" button will take users to for creating a new projecttheme.js
file as I anticipate textfields will be the same everywhere in the appname
like we used toProjectAPIService.js
fileSave
button to be disabled until all inputs are filledClose
button to redirect users to projects list page since the backend doesnt respond with necessary project id information that will be required to send a user to the project details pageScreenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)
Visuals before changes are applied
Visuals after changes are applied
Before Merging
POST
request that creates a new project with the id so we can redirect users from project creation form to project details page