JENKINS-75593: Use empty string for undefined referencedParameters #505
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.
The change in #467 has caused parameters without referenced parameters to no longer render correctly in certain conditions:
While it seems uncommon to use a Reactive Parameter without references, I rely on Reactive Reference parameters with no references for hidden values or to trigger custom JavaScript.
The undefined errors seem to only occur in pipelines. In freestyle jobs the value is an empty string if there are no referenced parameters. I'm thinking it should default to an empty string in both cases. This would maintain consistency between job types and prevent JS errors when accessing the referencedParameters property.
I can add some tests if this is an acceptable solution.