-
Notifications
You must be signed in to change notification settings - Fork 18
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
Allow configuring logos for multiple languages #1292
base: next
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
187ca44
to
8f5530d
Compare
This comment has been minimized.
This comment has been minimized.
8f5530d
to
827701c
Compare
827701c
to
4284ab7
Compare
4284ab7
to
c2a568c
Compare
c2a568c
to
9804557
Compare
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.
There are some things I would change about the backend implementation, I believe this can be implemented in less code. And I also would add a different check. I have not fully reviewed the frontend yet, as it might be useful to wait for the backend changes to properly assess how to best implement the frontend.
9804557
to
600137d
Compare
600137d
to
27de244
Compare
I did most of the things you commented on. I still need to do what you suggested in #1292 (comment), and contrary to what I said earlier, I would really appreciate if you could tackle the validation logic as laid out in #1292 (comment). Edit: Another thing I still need to address after the latest changes: The code as is right now doesn't know what to do when a wildcard ( |
27de244
to
e60b7bc
Compare
This will allow admins to configure logos in any number of languages, each with the optional properties of size (wide/narrow) and mode (light/dark). The language prop can also be omitted, in which case the respective logo will be used for all languages.
They now use the new configuration "syntax" for our logos.
This will now change the logo based on current language, if applicable logos exist.
e60b7bc
to
1fb48ca
Compare
This is a bit more explicit and flexible than the previous solution where `en` was always the default. Sadly, this is a breaking change for the configuration. In most cases, migrating is just replacing `en` with `default`.
This makes sure for every case/situation there is exactly one logo defined.
This will make it possible to configure logos for any number of languages (though for now, Tobira only knows what to do with english, german and non-language-specific logos).
This is a breaking change, as it changes the way logo files are configured. Previous configurations won't work anymore.
Specifics and examples for the new configuration will be available in our docs.
Closes #1271