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
FEAT(client, ui): separate ipv4 and ipv6 in ServerItem tooltip #5714
Conversation
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.
Once you have made all changes (just edit your commit and then force-push your branch), please also run scripts/updatetranslations.py
in order to update the source texts for the translations.
026ee81
to
f0a155f
Compare
Just for your information: The commits seem to have been associated with emails that are not connected to your GitHub accounts. This doesn't bother us, but I wanted to make you aware that right now the commits don't attribute authorship to your respective GitHub accounts ☝️ |
Do you happen to have a clang-format 10 installation at hand? If so, please run it on the source files you edited to bring them into the proper formatting. If not, let me know and I can do that for you. |
The "Addresses" field in the ServerItem tooltip shows both ipv4 and ipv6 addresses. The order of addresses in this field is not determined. In the wild it is randomized. As discussed in mumble-voip#5696 it is better to implement a concrete ordering to prevent user confusion. To further improve the readability of the addresses we split the addresses field in two fields called "IPv4 address" and "IPv6 address". The ipv4 address is now always shown above the ipv6 address. Implements mumble-voip#5696 Co-Authored-By: Thomas Pawelek <thomas.pawelek@stud.uni-hannover.de>
f0a155f
to
4d3f63a
Compare
The code should now be correctly formatted with clang-format 10. |
Thank you for your contribution 👍 |
The "Addresses" field in the ServerItem tooltip shows both ipv4 and ipv6
addresses. The order of addresses in this field is not determined.
In the wild it is randomized. As discussed in #5696 it is better to implement
a concrete ordering to prevent user confusion. To further improve the
readability of the addresses we split the addresses field in two fields
called "IPv4 address" and "IPv6 address". The ipv4 address is now always
shown above the ipv6 address.
Implements #5696
Co-Authored-By: GuybrushThreepwoodII
Checks