Explicitly convert params to integers where needed in previews #2735
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.
Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?
Fixes #2734.
When you change a param in lookbook, that value gets sent as a string, even if it is a number. We have different components where we allow changing the number of things rendered, and if you try to change the number, it errors currently because we are passing in a string instead of an integer.
This PR just updates those previews to call
.to_i
, if the param is present. I've confirmed that this fixes changing the params for these previews in lookbook.Risk Assessment
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.