Skip to content
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

Add error helpers for metadata settings inputs in form #5428

Closed
Tracked by #6218
ijreilly opened this issue May 15, 2024 · 6 comments
Closed
Tracked by #6218

Add error helpers for metadata settings inputs in form #5428

ijreilly opened this issue May 15, 2024 · 6 comments
Assignees
Labels
good first issue Good for newcomers

Comments

@ijreilly
Copy link
Collaborator

ijreilly commented May 15, 2024

Scope & Context

For now we are impeding users from trying to save an Object, a field or an option if the inputted value is not valid (because it starts with a digit or only contains empty char or is not transliterable, depending on the concerned data object). Let's add helpers in the form to help them understand what is wrong with their value (ex: "This field cannot be empty" / "Object names cannot start with digits".).

Expected behaviour can be clarified with @Bonapara

@Bonapara
Copy link
Member

image

We should use this design!

https://www.figma.com/design/xt8O9mFeLl46C5InWwoMrN/Twenty?node-id=3007-69739&t=vYBsvz4IWvZL44UI-11

charlesBochet added a commit that referenced this issue May 15, 2024
## Context 
Fixes #5403

Transliteration is now integrated to form validation through the schema.
While it does not impede inputting an invalid value, it impedes
submitting a form that will fail as the transliteration is not possible.
Until then we were only performing the transliteration at save time in
the front-end, but it's best to provide the information as soon as
possible. Later we will add helpers to guide the user (eg "This name is
not valid": #5428).

---------

Co-authored-by: Charles Bochet <[email protected]>
@t007rushi
Copy link
Contributor

@Bonapara this is closed?

@Bonapara
Copy link
Member

No! I just assigned you to it. Let me know if you don't want to handle it. If you do, thank you for contributing!

@t007rushi
Copy link
Contributor

Thanks @Bonapara will be happy to contribute, will ask if need any help

@ijreilly
Copy link
Collaborator Author

Hi @t007rushi , thank you for your interest in twenty!
This issue is just being fixed by a parallel issue that overlaps a bit with this one: #6094, so I think we can close this one now as there will be conflict.
Feel free to find another issue to work on if you like the project :)

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Product development ✅ Jul 15, 2024
@t007rushi
Copy link
Contributor

No issues @ijreilly
kudos for issue got solved
understanding/learning and contributing to the repo is motive
will pick another one 👍

arnavsaxena17 pushed a commit to arnavsaxena17/twenty that referenced this issue Oct 6, 2024
…tyhq#5430)

## Context 
Fixes twentyhq#5403

Transliteration is now integrated to form validation through the schema.
While it does not impede inputting an invalid value, it impedes
submitting a form that will fail as the transliteration is not possible.
Until then we were only performing the transliteration at save time in
the front-end, but it's best to provide the information as soon as
possible. Later we will add helpers to guide the user (eg "This name is
not valid": twentyhq#5428).

---------

Co-authored-by: Charles Bochet <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: ✅ Done
Development

No branches or pull requests

4 participants
@Bonapara @ijreilly @t007rushi and others