Update references to 'workflow' (from old 'valueName' parameter) #24054
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.
Overview
Update references to 'workflow' (from old 'valueName' parameter)
Before
We have deprecated
valueName
and the docs are updated to useworkflow
instead. There is handling to ensure both are passed toalterMailParams
and we have updated some places to passworkflow
, safe in the knowledge thatalterMailParams
will get both - but confusingly lots of places still passvalueName
After
valueName
is 'almost' gone. There is still the sync code and references in unit tests designed to check whatalterMailParams
gets.The api v3 code is a bit tricksy. Where we end up is that
workflow
, the oldvalueName
and the attempt to have a prettier variable for the apioption_value_name
) are all acceptedworkflow
is the promoted paramTechnical Details
Comments