MLE-25579 Can now specify transform params when writing a transform #1043
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.
When transforms did lack the power to declare
What parameters they would deign to receive,
Developers were left in dark despair,
With undocumented args they could not believe.
But lo! transformParams now graces the write,
A simple object of name and type pairs,
From xs:string? to xs:integer's might,
The query string now carries all affairs.
trans:flag and trans:count now ride along,
URL-encoded, proper, clean, and true,
The list endpoint sings a validating song,
Confirming params registered on cue.
So merge this branch with confidence and cheer,
For typed transform params are finally here!