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
The FullCalendar Angular docs require that the @fullcalendar/angular package go before any other fullcalendar-related package. Otherwise you'll get a JS error like Please import the top-level fullcalendar lib before attempting to import a plugin. Example configuration:
import{FullCalendarModule}from'@fullcalendar/angular';// the main connector. must go firstimportdayGridPluginfrom'@fullcalendar/daygrid';// a pluginimportinteractionPluginfrom'@fullcalendar/interaction';// a plugin
Also, the registerPlugins exists for a similar reason: to prevent the .component.ts file from importing its own plugin files, which might violate the ordering. Example:
It would be great to do away with this ordering restriction as well as registerPlugins. For an explanation of why this ordering restriction exists in the first place, see fullcalendar/fullcalendar#6371
The text was updated successfully, but these errors were encountered:
The FullCalendar Angular docs require that the
@fullcalendar/angular
package go before any other fullcalendar-related package. Otherwise you'll get a JS error likePlease import the top-level fullcalendar lib before attempting to import a plugin.
Example configuration:Also, the
registerPlugins
exists for a similar reason: to prevent the.component.ts
file from importing its own plugin files, which might violate the ordering. Example:It would be great to do away with this ordering restriction as well as
registerPlugins
. For an explanation of why this ordering restriction exists in the first place, see fullcalendar/fullcalendar#6371The text was updated successfully, but these errors were encountered: