Remove unused syntaxHighlighting field#195
Merged
cesan3 merged 1 commit intoApr 30, 2026
Merged
Conversation
The private boolean syntaxHighlighting field in ValidatingYamlParameterValue was never read, written, or exposed via getter/setter or @DataBoundSetter, and is not referenced from any Jelly view. Removing it as dead code.
cesan3
added
java
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
1 participant
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.
Summary
private boolean syntaxHighlightingfield fromValidatingYamlParameterValue. It has no getter, no setter, no@DataBoundSetter, is never read or written anywhere in the codebase, and is not referenced from any Jelly view — pure dead code.Test plan
mvn clean verifypassesgrep -r "syntaxHighlighting" src/returns no matches after the change