fix: ts types for headingValue
in CalendarHeading
and `RangeCalendarHeading components
#981
+8
β0
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.
π Linked issue
Resolves #638
β Type of change
π Description
This pull request addresses a TypeScript typing issue in the
CalendarHeading
component whereheadingValue
was implicitly typed asany
. The solution ensures explicit typing of the slot props, preventing further TypeScript errors and improving type safety.v-slot
usage to explicitly declare the type ofheadingValue
asstring
.Btw, I'm using Inertia.js with vite 6.0 with strict types
πΈ Screenshots (if appropriate)
π Checklist