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

Theme names #9401

Closed
wants to merge 1 commit into from
Closed

Theme names #9401

wants to merge 1 commit into from

Conversation

elizavetaRa
Copy link
Member

@elizavetaRa elizavetaRa commented Jul 12, 2023

Description

Adding the "theme name" property that should be visible for switcher of more than 2 themes
Relates to #9396

Related Issue

Motivation and Context

How Has This Been Tested?

  • test environment:
  • test case 1:
  • test case 2:
  • ...

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:

Open tasks:

  • ...

@update-docs
Copy link

update-docs bot commented Jul 12, 2023

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@elizavetaRa
Copy link
Member Author

@tbsbdr @pascalwengerter
To discuss: in the current implementation the keys "default" and "default-dark" for themes are handled as names in packages/web-runtime/src/composables/theme/useDefaultThemeName.ts. They are certainly not fitting as names to be shown for user.

  • Could they be renamed to themeId or
  • Or could we give more user-friendly strings for these keys like "Default light" and "Default dark"? Then there would be no need to add an extra-property

@dschmidt
Copy link
Member

I think it's reasonable to have a technical and a user visible name - we just need to make sure the user visible strings are translated

@pascalwengerter
Copy link
Contributor

I think it's reasonable to have a technical and a user visible name - we just need to make sure the user visible strings are translated

Translations are tough-to-impossible for custom themes though (unless I'm missing something)?
Agreed in general and happy to work on it in the upcoming weeks (but after the CERN bucket list?)

@dschmidt
Copy link
Member

I think it's reasonable to have a technical and a user visible name - we just need to make sure the user visible strings are translated

Translations are tough-to-impossible for custom themes though (unless I'm missing something)? Agreed in general and happy to work on it in the upcoming weeks (but after the CERN bucket list?)

I especially meant the themes we are shipping, if someone ships custom themes they can ship custom translations for theme names as well 😎

@pascalwengerter
Copy link
Contributor

Closing in favor of #9698, thanks for the initiative and input!

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

Successfully merging this pull request may close these issues.

Provide nicer-to-read names for themes
3 participants