-
Notifications
You must be signed in to change notification settings - Fork 227
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
Server: Add --serverinfo ISO country code support #2841
Server: Add --serverinfo ISO country code support #2841
Conversation
Marking it as Draft to prevent accidential merges before #2829 is merged. Feel free to un-mask afterwards. |
I'm hoping to get this in to 3.9.1 - mostly because I'd love to get away from the numbers in the server info :). 3.9.1 may be a bug fix release but I see fixing server info handling as one of the "major selling points" of the release! |
c60bc81
to
a58d806
Compare
a58d806
to
da1c9ae
Compare
bf309e1
to
0a76163
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.
Besides my comment, happy to approve.
With this change, --serverinfo gains support for two-letter ISO country codes such as "de", "gb", "nl", "fr". Numeric Qt5-style codes keep working as expected. Fixes: jamulussoftware#2362
0a76163
to
5b2c2de
Compare
Opened jamulussoftware/jamuluswebsite#822 for the documentation. Therefore removing the needs-documentation label here. As stated, this is totally optional and doesn't have to be integrated at 3.9.1 release time. |
As it's small, I've merged it. |
Short description of changes
With this change, --serverinfo gains support two-letter ISO country codes such as "de", "gb", "nl", "fr". Numeric Qt5-style codes keep working as expected.
To simplify user-side debugging, the
--serverinfo
parsing now contains logging for the final values (or a warning in case of parsing problems).CHANGELOG: Server: Added support for ISO country codes (de, gb, nl, ...) in --serverinfo.
Context: Fixes an issue?
Fixes: #2362
Related: #2829 (comment)
Does this change need documentation? What needs to be documented and how?
As this is a (tiny) new feature, docs would be useful, but not mandatory. This is not a breaking change. Delaying the docs update would be no problem.
Status of this Pull Request
Ready
What is missing until this pull request can be merged?
Checklist