Use REST config instead of ClientConfig #66
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the
NewWhoCan
method to take arest.Config
objectinstead of a
ClientConfig
object. This allows the consumer of the APIto use a custom
rest.Config
object rather than relying on the onecreated from the
ClientConfig
object.This also removes the
clientConfig
field from theWhoCan
object. Itis only used within the
ActionFrom
method, and it is passed in as anargument. As a result, there is no need to store it on the
WhoCan
object.
Signed-off-by: Bridget McErlean [email protected]