CalendarHeading v-slot prop headingValue causes implicit any

[MaxHeilmann2004]

Hi, so I recently updated my dependencies after which CalendarHeading component from shadcn-vue caused a implicit any.
Here is the whole error:

src/components/ui/calendar/CalendarHeading.vue:18:32 - error TS7022: 'headingValue' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

18     <CalendarHeading v-slot="{ headingValue }" :class="cn('text-sm font-medium', props.class)" v-bind="forwardedProps">
                                  ~~~~~~~~~~~~

This seems like a problem caused by radix-vue, since the CalendarHeading component in line 18 is imported from radix-vue.
Now my question arises, is this a problem with my configuration somehow or is this a bug that hasn't been addressed yet.

Here are the versions from my package.json:

{
    "vue": "3.5.13",
    "radix-vue": "1.9.12",
    "typescript": "5.7.3"
}

[adlermore]

Hi, so I recently updated my dependencies after which CalendarHeading component from shadcn-vue caused a implicit any. Here is the whole error:

src/components/ui/calendar/CalendarHeading.vue:18:32 - error TS7022: 'headingValue' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

18     <CalendarHeading v-slot="{ headingValue }" :class="cn('text-sm font-medium', props.class)" v-bind="forwardedProps">
                                  ~~~~~~~~~~~~

This seems like a problem caused by radix-vue, since the CalendarHeading component in line 18 is imported from radix-vue. Now my question arises, is this a problem with my configuration somehow or is this a bug that hasn't been addressed yet.

Here are the versions from my package.json:

{
    "vue": "3.5.13",
    "radix-vue": "1.9.12",
    "typescript": "5.7.3"
}

It seems like this issue is related to TypeScript's handling of implicit types in combination with the CalendarHeading component from radix-vue. The error you're seeing happens when TypeScript cannot infer the type of headingValue, so it defaults to any.

This could be caused by:

Missing Type Annotations: The headingValue is missing an explicit type in the v-slot. To resolve this, you can try explicitly defining the type in your template.

TypeScript Configuration: You might want to check your tsconfig.json and ensure that noImplicitAny is set to true. This forces TypeScript to catch these implicit any types.

Radix-Vue Typing Issue: If the radix-vue package itself doesn't provide sufficient TypeScript types for this component, it could indeed be a bug or a limitation in radix-vue. You could check the package's issue tracker to see if this has already been addressed.

To fix the immediate issue, try updating your component like this: