-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Cleanup ProvReq wrapper #6670
Cleanup ProvReq wrapper #6670
Conversation
5057e53
to
7ff9480
Compare
/assign @towca |
/lgtm The change itself LGTM, but I'm wondering about the motivation behind it. It seems like the wrapper was designed as a translation layer between different ProvReq API versions. Do you think this won't be needed after all? What happens when we introduce v1 ProvReq? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: towca, yaroslava-serdiuk The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold API is unlikely to change much, but there are a lot of code duplication in current version of wrapper. |
What type of PR is this?
/kind cleanup
Special notes for your reviewer:
Does this PR introduce a user-facing change?