Custom Default Event Duration - Request.

[Jacob-Daniel]

Hi,

Thanks for your work on this.

I am wanting to use this plugin for a campsite booking application, I would like to set the Default Duration to allDay. I have run into trouble trying to set this up:

Summary of Issues

Environment: Strapi Version: 4.25.x Plugin Name: @offset-dev/strapi-calendar Steps Taken: Installation of the Plugin:

Installed @offset-dev/strapi-calendar using a package manager (pnpm).

At this point, the install is all good and the plugin is available in admin.

Initial Plugin Configuration: Configured the plugin in config/plugins.js:

module.exports = ({ env }) => ({
  "strapi-calendar": {
    enabled: true,
  },
});

Encountered the following error:

Error: Error loading the plugin strapi-calendar because strapi-calendar is not installed. Adjusting Plugin Name, modified the configuration to:

module.exports = ({ env }) => ({
  "@offset-dev/strapi-calendar": {
    enabled: true,
  },
});

Received the error:

Error: Plugin name "@offset-dev/strapi-calendar" is not in kebab (an-example-of-kebab-case).
Using Kebab-Case:

Attempted to set the plugin in kebab-case with:

module.exports = ({ env }) => ({
  'strapi-calendar': {
    enabled: true,
    defaultDuration: 1440, // Set full day to 24 hours
  },
});

Encountered the same error regarding installation:

Error: Error loading the plugin strapi-calendar because strapi-calendar is not installed.
Custom Resolve Path:

Attempted to resolve the plugin using a custom path:

module.exports = ({ env }) => ({
  'strapi-calendar': {
    enabled: true,
    resolve: './src/plugins/@offset-dev/strapi-calendar',
  },
});

Received the same installation error. Error Details:

Error: Plugin not installed despite verification that the plugin was included in the project.
Error: Plugin name not in the expected kebab-case format.
Error: Issues with loading the plugin configuration leading to a failure in starting Strapi.

Current Status: The Strapi application fails to start due to plugin configuration issues, specifically with naming conventions and installation recognition.

Thank you,

Jacob