-
Notifications
You must be signed in to change notification settings - Fork 5
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
Inconsistency with null and empty fragment in URI #338
Comments
I try to follow Android's Uri so if the behavior you're seeing matches that, I would leave it. Otherwise please feel free to file a PR. |
I will check URI implementation in Android, thank you |
I have checked the Android sources and it looks like the behavior in Android's URI is the same. |
For reference: https://issuetracker.google.com/issues/346174910 |
Absolutely, thank you! |
Hi,
I have noticed that the URI with an empty (not null) fragment parsed from the string is not equal to a URI with an empty fragment created with
Uri.Builder
(the URI created from the builder does not have#
in the end if an empty fragment was set).I would think that if a fragment is empty the
#
should be added at the end of the URI string representation.If you agree, I will create a PR with changes and tests.
Here you can find a small example to reproduce the case:
Thank you!
The text was updated successfully, but these errors were encountered: