fix(ui): fix __splitDate function: invalid call function 'pad' for date.year #17907
+1
−1
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.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
dev
branch (orv[X]
branch)fix: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
There is an animation bug in the calendar component. After rendering, the first call to switch between month or year shows the wrong animation - the slide always flips to the right. This can be seen in any example in the documentation for the
QDate
component, when v -model is defined.QDate._.Quasar.Framework.-.Google.Chrome.2025-03-18.13-36-48.mp4
After searching, I found that in the
QDate.js
file in thegetViewModel()
function in the returned object, thedateHash
field comes in the format002025/18/03