Skip to content
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

Use REST config instead of ClientConfig #66

Merged
merged 1 commit into from
Feb 19, 2020

Conversation

zubron
Copy link
Contributor

@zubron zubron commented Feb 18, 2020

This updates the NewWhoCan method to take a rest.Config object
instead of a ClientConfig object. This allows the consumer of the API
to use a custom rest.Config object rather than relying on the one
created from the ClientConfig object.

This also removes the clientConfig field from the WhoCan object. It
is only used within the ActionFrom method, and it is passed in as an
argument. As a result, there is no need to store it on the WhoCan
object.

Signed-off-by: Bridget McErlean [email protected]

@lizrice
Copy link
Contributor

lizrice commented Feb 18, 2020

Codecov Report

Merging #66 into master will increase coverage by 0.18%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #66       /-   ##
==========================================
  Coverage   70.54%   70.72%    0.18%     
==========================================
  Files           5        5              
  Lines         387      386       -1     
==========================================
  Hits          273      273              
  Misses         99       98       -1     
  Partials       15       15              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 922e198...f4fe984. Read the comment docs.

@danielpacak danielpacak self-requested a review February 19, 2020 09:47
This updates the `NewWhoCan` method to take a `rest.Config` object
instead of a `ClientConfig` object. This allows the consumer of the API
to use a custom `rest.Config` object rather than relying on the one
created from the `ClientConfig` object.

This also removes the `clientConfig` field from the `WhoCan` object. It
is only used within the `ActionFrom` method, and it is passed in as an
argument. As a result, there is no need to store it on the `WhoCan`
object.

Signed-off-by: Bridget McErlean <[email protected]>
@codecov-io
Copy link

codecov-io commented Feb 19, 2020

Codecov Report

Merging #66 into master will increase coverage by 0.18%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #66       /-   ##
==========================================
  Coverage   70.46%   70.64%    0.18%     
==========================================
  Files           5        5              
  Lines         386      385       -1     
==========================================
  Hits          272      272              
  Misses         99       98       -1     
  Partials       15       15              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f549a4c...4e273ca. Read the comment docs.

Copy link
Contributor

@danielpacak danielpacak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @zubron LGTM!

@danielpacak danielpacak merged commit 3b55776 into aquasecurity:master Feb 19, 2020
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.

4 participants