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

[Feedback]: Inconsistencies between country codes format in configuration makes it easy to crash the GUI app #674

Open
abaurens opened this issue Apr 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@abaurens
Copy link

abaurens commented Apr 25, 2024

Type

Both

Suggestion

In the cli-defaults.yml config, the dlsubs field expects a 2-char ISO 3166-1 country code while dubLang and defaultAudio both expects a 3-char ISO 3166-2 one.

Even tho this is documented in their respective sections of the documentation:

It is missleading when working with the GUI version and editing the config manually, as the default for dlsubs is all which gives no indication about the expected format (unlike dubLang and defaultAudio which both defaults to jpn).

This results in easy mistakes which makes the app silently crash upon service selection because it doesn't recognize the 3-char code.


Here are a few suggestions that could fix the issue, even tho I don't know if they are all technically applicable:

  • Add indications about the expected format in the comment above the fields.
  • Prevent the GUI app from crashing upon service selection when the CLI fails to execute and add an error message to the GUI and/or to the log file.
  • Changing dlsubs to ISO 3166-2 to match dubLang and defaultAudio's format.
  • Making dubLang, dlsubs and defaultAudio format neutral (accept both format and convert to the expected one internaly).
  • Hardcode default values (or don't pass the argument to CLI) whenever the value in config file is unknown/unsuported (possiblywith an error message in the GUI to warn the user that it's config is being ignored).
@abaurens abaurens added the enhancement New feature or request label Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant