-
Notifications
You must be signed in to change notification settings - Fork 0
Feat: Basic languages page #128
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
Conversation
…ntegration test cases
sjaghori
left a comment
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.
Thank you for the PR 🚀
There are some minor issues with the validation, woud you like to have a look at that?
sjaghori
left a comment
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 job! 🚀 I think we can merge this already.
There are just three things we should discuss:
- IMO it makes more sense to automatically select the fallback language when a user adds a new language. It is perfectly fine to give them the option to deselect the fallback language or choose another fallback language.
- We should consider renaming base language to default language
- Adding a modal when there are unsaved changes or removing the save option, adding the functionality for what you see is what is in the db.
Will create a follow up PR for your third point. Will introduce both, improved save button state as well as the modal if there are stale changes. Moreover, I will set a the base language as fallback after creating a new language. |

This PR adds the basic languages page including the following features:
What is missing and will be done in a subsequent PR:
Fallback language input field as select with available optionsConfirmation Modal before deleting a language