You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v4 both ResourceFunc and ResourceInput were exported and users could depend on these types. In v5 it seems that these two types didn't make it to the export list. A good reason for also exporting would be symmetry: EventSourceInput and EventSourceFunc are exported so as a user I would expect the same for resources. Would you consider exporting them?
If you're ok with this, I would gladly make a PR to fullcalendar-schedule as this is a trivial change.
The text was updated successfully, but these errors were encountered:
import { RawOptionsFromRefiners } from '@fullcalendar/core';
import { ResourceSourceInput } from '@fullcalendar/resource-common';
type Unpacked<T> = T extends (infer U)[] ? U : T;
/**
* The `ResourceFunc` type is not exported since v5 of fullcalendar. This
* hack here works around that by extracting the `ResourceFunc`.
*/
export type ResourceFunc = Extract<ResourceSourceInput, (...args: any) => any>;
/**
* The `ResourceInput` type is not exported since v5 of fullcalendar. This
* hack here works around that by extracting the `ResourceInput`.
*/
export type ResourceInput = Unpacked<Exclude<ResourceSourceInput, string | ResourceFunc | RawOptionsFromRefiners<any>>>;
Checklist
Please mark these items with an [x]
Feature Description
In v4 both
ResourceFunc
andResourceInput
were exported and users could depend on these types. In v5 it seems that these two types didn't make it to the export list. A good reason for also exporting would be symmetry:EventSourceInput
andEventSourceFunc
are exported so as a user I would expect the same for resources. Would you consider exporting them?If you're ok with this, I would gladly make a PR to fullcalendar-schedule as this is a trivial change.
The text was updated successfully, but these errors were encountered: