refactor AdminFunction Args #210
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…object for both defined functions and custom ones. ignore plugin ops and routines in ispolicyempty (#209)
joshua-roberts
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR changes the Args implementation for AdminFunctions (operations and routines). Instead of an AdminFunction defining the return type and args type as generics, it will only define the return type. Args has been made a concrete class wrapper for a Map<FormalParameter, Object>. It is up to the AdminFunction implementation to define and document the expected parameters and the caller to match the expected parameters.
This was done to avoid the situation of having an AdminFunction object with wildcard and not being able to directly call it's methods without the concrete corresponding Args class.