V6 Tasks

[edalzell]

• remove collection config now that we can support more than one collection
• to due the above, adjust the computed fields to loop through the new config (with multiple collections). Note they may not have an location fields set, which means the collections are values not keys
• add location as computed field maybe?
• drop old version constraints (Forma/Statamic/Laravel). Only support Statamic v6 (and only the Laravel versions that supports) due to Vue3 CP
• Upgrade fieldtypes to Vue3 -> no Vue components
• Make sure carbon v3 works the same for Carbon::setWeekStartsAt(day: $weekStartDay)
• [6.x] Remove use of deprecated nesbot/carbon methods #106
• Refactor the Ics downloads, duplicate code in the address/description/url fields
• remove location_field config. If they want to customize, use a computed field. remove location() method in Event.php
• use Group field type for all "event" fields?

Post V6 tasks

• expose the collection/location_field config to the CP

[enderandpeter]

Hello @edalzell. I am a developer for a company using Statamic and this excellent calendar events plugin. We would like to upgrade to the latest Statamic and upgrade other packages, but unfortunately the transformstudios/events package's use of Carbon::setWeekStartsAt is preventing the upgrade. You are surely aware but I am now learning the issue is that the method was deprecated in Carbon v2 but is now removed in Carbon v3.

Forgive me in that I am just now catching up but I see how a few years ago you had a conversation with a Carbon developer who provided another solution that should work with Carbon v3.

Is this something that can only be targeted for V6, or can it be done in V5 of this project? I need to study this situation a bit more, but I was hoping to make a PR for V5 that will address this.

Thank you very much.

[edalzell]

The latest Statamic still supports Carbon v2, manually require that in your project and it should be fine.

Was planning on waiting until Statamic v6 is release for a major upgrade.

[edalzell]

That being said, I'm not a against a PR to resolve it, as long as the solution still works in carbon v2

[enderandpeter]

Thank you so much for the advice. Yes I am seeing that after locking nesbot/carbon at the latest version 2 with the command composer require nesbot/carbon:^2 and then running composer update it is still able to upgrade statamic/cms to 5.49.0 and transformstudios/events to 5.6.0. When I go to the Updates page in the Statamic dashboard, it still says there are 2 updates available without indicating on the page what is actually out of date. Nevertheless, I think this might work for now.

Thank you!