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

Should locale be a select instead of a text input? #19

Open
psrpinto opened this issue Jan 25, 2024 · 2 comments
Open

Should locale be a select instead of a text input? #19

psrpinto opened this issue Jan 25, 2024 · 2 comments

Comments

@psrpinto
Copy link
Member

Currently the Locale form input is a text field and the user can input any text, e.g foo.

I'm wondering, should it be a select instead, with only the locales that exist in GlotPress db?

@psrpinto psrpinto added this to the Initial release milestone Jan 25, 2024
@trymebytes
Copy link
Collaborator

Yea, I agree that it should be a select dropdown. @akirk and I had a discussion about this and we agreed to remove/hide this locale field for now. So, after the initial release, we can continue working on it.

@psrpinto psrpinto removed this from the Initial release milestone Jan 30, 2024
@amieiro
Copy link
Collaborator

amieiro commented Feb 12, 2024

Yes, we should have a multi selection dropdown, so the user can select more than one language for the event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants