Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

CRDCDH-35 Redesign Form Section B #9

Merged
merged 27 commits into from
Jun 26, 2023
Merged

CRDCDH-35 Redesign Form Section B #9

merged 27 commits into from
Jun 26, 2023

Conversation

Alejandro-Vega
Copy link
Collaborator

Overview
This PR is a redesign of Form Section B for the ticket CRDCDH-35 The original implementation for the section was created by @amattu2.

  • Modified spacing and positioning of Form B
  • Updated styling and spacing for every type of input (textfield, select, autocomplete, etc.)
  • Updated styling and spacing for each section of the form
  • Added section for Planned Publications
  • Imported icons (dropdown arrows, and calendar) and added them as adornment to corresponding inputs
  • Created DatePickerInput and added Dayjs dependency necessary for the DatePicker MUI component. If we want to switch date library adapters it should be addressed.

…t, while still maintaining consistent button styling
…he SectionGroup itself. Also added the ability to include a description and an endButton beside the title of a SectionGroup
…ion and content. Create a tooltip component to better match the styling of our tooltips. I also created DatePickerInput, but it is in an unfinished state and used as a placeholder currently
…ut, autocomplete input, and select input styling and props
…publications and repositories gets reset to empty array if none are provided. Also updated AddRemoveButton to use styled instead as well as adding convenient props
@Alejandro-Vega Alejandro-Vega marked this pull request as draft June 22, 2023 20:19
Copy link
Collaborator

@jonkiky jonkiky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! -- We may need to think about how to improve the way to styling. Should we need to move some styles into global sharing theme?

@Alejandro-Vega Alejandro-Vega marked this pull request as ready for review June 23, 2023 16:19
@Alejandro-Vega
Copy link
Collaborator Author

@jonkiky I agree, we should find a better solution for styling and move common/repeated styling into global theme. The inputs for example all have very similar styling.

@jonkiky jonkiky merged commit f310db3 into dev Jun 26, 2023
@jonkiky jonkiky deleted the CRDCDH-35-Redesign branch June 27, 2023 13:28
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants