Skip to content

Add Overload to OAuthParameters.toReference which Accepts an Existing Reference #1240

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

Merged
merged 2 commits into from
Nov 5, 2016
Merged

Add Overload to OAuthParameters.toReference which Accepts an Existing Reference #1240

merged 2 commits into from
Nov 5, 2016

Conversation

romeara
Copy link
Contributor

@romeara romeara commented Oct 4, 2016

Prevent unpacking and repacking of reference instances when adding client query information from OAuthParameters by providing a call to apply the query to an existing reference.

When using the existing APIs, I found that a common pattern emerged where a Reference was present, but had to be serialized and deserialized to and from a String in order to add OAuth query parameters. If the OAuthParameters instance offered a toReference call which took a reference object, this pattern could be simplified for clients.

Prevent unpacking and repacking of reference instances when adding
client query information from OAuthParameters by providing a call to
apply the query to an existing reference
@thboileau
Copy link
Contributor

many thanks for your contribution!
It is now part of the master and 2.3 branches.
The fix will be released with 2.3.8

@thboileau thboileau merged commit 81c2f9f into restlet:master Nov 5, 2016
@romeara romeara deleted the dev/romeara/oauth-param-to-ref branch November 5, 2016 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants