[Painless] Allow statically imported methods without whitelisted class #34370
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
jdconrad
added
>bug
:Core/Infra/Scripting
Collaborator
|
Pinging @elastic/es-core-infra |
Contributor
Author
|
@rjernst Thanks for the review! Will commit as soon as CI passes. |
jdconrad
added a commit
that referenced
this pull request
Oct 10, 2018
…#34370) This removes the extraneous check to see if the class for a statically imported method is already whitelisted, so a statically imported method can be whitelisted independently.
kcm
pushed a commit
that referenced
this pull request
Oct 30, 2018
…#34370) This removes the extraneous check to see if the class for a statically imported method is already whitelisted, so a statically imported method can be whitelisted independently.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Currently, a class must be whitelisted separately to allow a statically imported method to also be whitelisted. This removes the extraneous check to see if the class for a statically imported method is already whitelisted, so a statically imported method can be whitelisted independently.