Socket
Socket
Sign inDemoInstall

@schedule-x/calendar

Package Overview
Dependencies
Maintainers
0
Versions
125
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@schedule-x/calendar - npm Package Compare versions

Comparing version 1.46.6 to 1.46.7

25

dist/core.cjs.d.ts

@@ -206,5 +206,2 @@ import { Signal } from "@preact/signals";

};
type RecursivePartial<T> = {
[P in keyof T]?: T[P] extends (infer U)[] ? RecursivePartial<U>[] : T[P] extends object | undefined ? RecursivePartial<T[P]> : T[P];
};
interface PluginBase {

@@ -214,12 +211,22 @@ name: string;

/**
* use a recursive partial on the $app interface, in order to not break any third party plugins
* when we add new properties to the $app interface
* Allow implementers to dynamically add any properties to the global app object as they see fit.
* In order to avoid conflict with future properties added to the library, we recommend
* using the unique prefix `$` for any custom properties added to the global app object.
* for example $app['$websocketService'] = new WebsocketService().
* Adding properties to existing sub-objects is discouraged, since this will make your application more
* brittle to future changes in the library.
* */
beforeInit?($app: RecursivePartial<CalendarAppSingleton>): void;
// eslint-disable-next-line @typescript-eslint/no-explicit-any
beforeInit?($app: CalendarAppSingleton | any): void;
// TODO v2: change to `onRender` and remove $app parameter
/**
* use a recursive partial on the $app interface, in order to not break any third party plugins
* when we add new properties to the $app interface
* Allow implementers to dynamically add any properties to the global app object as they see fit.
* In order to avoid conflict with future properties added to the library, we recommend
* using the unique prefix `$` for any custom properties added to the global app object.
* for example $app['$websocketService'] = new WebsocketService().
* Adding properties to existing sub-objects is discouraged, since this will make your application more
* brittle to future changes in the library.
* */
init?($app: RecursivePartial<CalendarAppSingleton>): void;
// eslint-disable-next-line @typescript-eslint/no-explicit-any
init?($app: CalendarAppSingleton | any): void;
destroy?(): void;

@@ -226,0 +233,0 @@ }

@@ -206,5 +206,2 @@ import { Signal } from "@preact/signals";

};
type RecursivePartial<T> = {
[P in keyof T]?: T[P] extends (infer U)[] ? RecursivePartial<U>[] : T[P] extends object | undefined ? RecursivePartial<T[P]> : T[P];
};
interface PluginBase {

@@ -214,12 +211,22 @@ name: string;

/**
* use a recursive partial on the $app interface, in order to not break any third party plugins
* when we add new properties to the $app interface
* Allow implementers to dynamically add any properties to the global app object as they see fit.
* In order to avoid conflict with future properties added to the library, we recommend
* using the unique prefix `$` for any custom properties added to the global app object.
* for example $app['$websocketService'] = new WebsocketService().
* Adding properties to existing sub-objects is discouraged, since this will make your application more
* brittle to future changes in the library.
* */
beforeInit?($app: RecursivePartial<CalendarAppSingleton>): void;
// eslint-disable-next-line @typescript-eslint/no-explicit-any
beforeInit?($app: CalendarAppSingleton | any): void;
// TODO v2: change to `onRender` and remove $app parameter
/**
* use a recursive partial on the $app interface, in order to not break any third party plugins
* when we add new properties to the $app interface
* Allow implementers to dynamically add any properties to the global app object as they see fit.
* In order to avoid conflict with future properties added to the library, we recommend
* using the unique prefix `$` for any custom properties added to the global app object.
* for example $app['$websocketService'] = new WebsocketService().
* Adding properties to existing sub-objects is discouraged, since this will make your application more
* brittle to future changes in the library.
* */
init?($app: RecursivePartial<CalendarAppSingleton>): void;
// eslint-disable-next-line @typescript-eslint/no-explicit-any
init?($app: CalendarAppSingleton | any): void;
destroy?(): void;

@@ -226,0 +233,0 @@ }

@@ -206,5 +206,2 @@ import { Signal } from "@preact/signals";

};
type RecursivePartial<T> = {
[P in keyof T]?: T[P] extends (infer U)[] ? RecursivePartial<U>[] : T[P] extends object | undefined ? RecursivePartial<T[P]> : T[P];
};
interface PluginBase {

@@ -214,12 +211,22 @@ name: string;

/**
* use a recursive partial on the $app interface, in order to not break any third party plugins
* when we add new properties to the $app interface
* Allow implementers to dynamically add any properties to the global app object as they see fit.
* In order to avoid conflict with future properties added to the library, we recommend
* using the unique prefix `$` for any custom properties added to the global app object.
* for example $app['$websocketService'] = new WebsocketService().
* Adding properties to existing sub-objects is discouraged, since this will make your application more
* brittle to future changes in the library.
* */
beforeInit?($app: RecursivePartial<CalendarAppSingleton>): void;
// eslint-disable-next-line @typescript-eslint/no-explicit-any
beforeInit?($app: CalendarAppSingleton | any): void;
// TODO v2: change to `onRender` and remove $app parameter
/**
* use a recursive partial on the $app interface, in order to not break any third party plugins
* when we add new properties to the $app interface
* Allow implementers to dynamically add any properties to the global app object as they see fit.
* In order to avoid conflict with future properties added to the library, we recommend
* using the unique prefix `$` for any custom properties added to the global app object.
* for example $app['$websocketService'] = new WebsocketService().
* Adding properties to existing sub-objects is discouraged, since this will make your application more
* brittle to future changes in the library.
* */
init?($app: RecursivePartial<CalendarAppSingleton>): void;
// eslint-disable-next-line @typescript-eslint/no-explicit-any
init?($app: CalendarAppSingleton | any): void;
destroy?(): void;

@@ -226,0 +233,0 @@ }

{
"name": "@schedule-x/calendar",
"version": "1.46.6",
"version": "1.46.7",
"description": "Schedule-X calendar component",

@@ -40,3 +40,3 @@ "author": {

"homepage": "https://schedule-x.dev",
"gitHead": "f35c0d86451edc0708328c9401c77a81aeed4b8a"
"gitHead": "83b2168f3603b96646015af536ac138f5ed983cc"
}

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc