RANGER-5694 : Refactor policy condition rendering component to ensure layout stability#1082
Merged
Merged
Conversation
… layout stability
dhavaljrajpara
approved these changes
Jul 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What changes were proposed in this pull request?
Need code refactoring to handle rendering policy condition gracefully during policy view from UI.
Fix is required for
ozone-sts actionfeature, where user can disable/enable the feature leaving redundant policy condition for action-matches which needs to be handled correctly on UI without any issue.How was this patch tested?
Tested Ranger Admin UI coming up successfully with this changes.
Successful completion of build command :
mvn clean compile package -DskipTests