-
Notifications
You must be signed in to change notification settings - Fork 22
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
More restrictive API for String arguments #185
Comments
Search and find all API constructors that use String. |
Greetings Sir @francis-pouatcha , should this first of all be a documentation on URL-Safe Strings with regards to an API. Need more clarification on this ticket before working on it. |
It is about locating which rest API have unsafe strings in their parameter. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently some String based constructors, factory methods that are intended for internal use (i.e. Uri, BasePrivateResource.forPrivate ...) are not safe to use with non-url safe Strings. While it does not affect global usage as *Request api can accept any type of String, it is better to hide those String (Uri, BasePrivateResource.for..) constructors as implementation detail if needed and expose url-safe variants.
The text was updated successfully, but these errors were encountered: