feat: update generate ticks into an array of properties for each axis #19850
+196
−90
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.
Follow-up to #19839 - we need to separate the control of the tick generation for each axis, as there will be cases where a user wants to control tick generation on one axis but not both. Also, the property should be an array of strings due to Giraffe's extreme flexibility in its configuration. (Giraffe uses 3 properties to control the tick generation, and any combination of the 3 properties including being missing or null works in the config.) To capture this flexibility for the user, we save the properties selected by the user in an array of strings.
Also, removed the tick generation properties from
CheckView
everywhere to match the swagger.yml