-
Notifications
You must be signed in to change notification settings - Fork 2
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
refactor: Editor forms tidy up and unify #3324
Conversation
Removed vultr server and associated DNS entries |
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 stuff! Visually all good, and very well organised and clear PR 👍
Happy to approve and merge once General Settings is commented back out until this is feature-complete.
export default function InputLabel(props: { | ||
label: string; | ||
children: ReactNode; | ||
hidden?: boolean; | ||
htmlFor?: string; | ||
id?: string; | ||
}) { |
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.
export default function InputLabel(props: { | |
label: string; | |
children: ReactNode; | |
hidden?: boolean; | |
htmlFor?: string; | |
id?: string; | |
}) { | |
export default function InputLabel(props: PropsWithChildren<{ | |
label: string; | |
hidden?: boolean; | |
htmlFor?: string; | |
id?: string; | |
}>) { |
nit: A little bit easier / simpler / better matches our code style 👌
Take a look at https://blog.logrocket.com/react-children-prop-typescript/
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.
Thanks, have updated
<InputGroup label="Why it matters"> | ||
<InputRow> | ||
<InputGroup flowSpacing> | ||
<InputLabel label="Why it matters"> |
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.
Do we want to remove the placeholder
values now if we're adding labels here?
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.
Good shout, the label + placeholder combo is already in place but it makes sense to have one or the other.
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.
Nice to also pick up changes here 🙌
Thanks for the review @DafyddLlyr , updated commit incoming with your suggestions + general settings commented out. |
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.
Perfect!
What does this PR do?
Refactors settings pages to use a simplified and unified structure.
Summary of changes:
<InputLabel>
for editor<EditorRow>
renamed to<SettingsSection>
to differentiate from<ModalSection>
as used in the graph editor<InputDescription>
renamed to<SettingsDescription>
To do before merging