fix: Fix logic for determining parameter types #1194
Merged
+25
−14
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.
Context
screwdriver-cd/models#630 modified the API response to always return a default field. This broke the previous assumption that minimum number of keys in the response object is 1.
#1189 added in a fix for the change in the API object, however there are a few other places in the UI code that used the same logic and needs to be updated.
Objective
Add a new utility function that is less fragile to determine whether a parameter is a pipeline level parameter. Updates all instances where determining if a parameter is a pipeline parameter is manually done.
References
License
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.