-
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
feat: team_settings
form error validation
#3368
Conversation
Removed vultr server and associated DNS entries |
The
|
Error Message GuidanceThe tone of voice guiding the error messaging follows information here: How to write good planning service content |
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.
Happy to merge following a few (very very minor!) fixes.
|
||
export interface Props { | ||
label?: string; | ||
inline?: boolean; | ||
color?: string; | ||
errorMessage?: string | undefined; |
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.
errorMessage?: string | undefined; | |
errorMessage?: string; |
nit: This is the same thing but a bit more terse and matches our code style. The ?
following the property name indicates that this property can be undefined
.
</Popover> | ||
) : null} | ||
</Root> | ||
<ErrorWrapper error={props.errorMessage || undefined} id="settings-error"> |
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.
We should use a unique id here, for example colour-picker
What does this PR do?
Following previous work done on
team_settings
form in the Editor: #3366This PR will introduce the Error Handling while making changes to shared
SettingsForm
to handle error messaging on an input level rather than form level.The only change to an Input Component will be to the
<ColourPicker>
which is used in theTheme
settings forms. The properrorMessage
has been added to the<ColourPicker>
component to enable this input level error messaging