fix(VDataFooter): better handle custom item options #8029
Merged
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.
fixes #8026
Description
When providing custom itemsPerPageOptions, if the current item did not exist in the options, it was pushed into the array. This means if no options are provided, 10 is the default and was being pushed into the array.
Now the system simply determines if the provided itemsPerPage exists in the items and if not, the first item is selected.
Motivation and Context
itemsPerPage has a default value of 10, which consequently was getting pushed into the footers items array because it was a value that did not exist within the provided list. This causes issues when adding custom itemsPerPageOptions that does not contain the value 10, (or whatever value is defined for the options).
How Has This Been Tested?
jest / visually
Markup:
Types of changes
Checklist:
master
for bug fixes and documentation updates,dev
for new features and breaking changes).