Work-Related/events
Work-Related/events
1
0
mirror of https://github.com/werkraum-media/events.git synced 2024-06-02 18:08:50 +02:00
Code Issues Activity
events/Documentation/Changelog/3.5.0.rst
Daniel Siepmann 27ee70d0cf
Add event to modify categories during destination.one import (#34) 
A new PSR-14 event is added that allows to modify the categories to be
assigned to an event.
The event itself (including already existing categories) as well as the
list of categories to be used after import are available.
It is possible to change the categories to be assigned, e.g. keep some
of the existing categories.

That way it is possible for installations to add custom categories to
events.

Relates: #10623
2023-08-14 12:09:28 +02:00

1.6 KiB
Raw Permalink Blame History

3.5.0

Breaking

  • We migrated away from Extbase Category model. This is technically breaking, but we don't consider it breaking as this should be an internal detail. Still this might break if you have type checks.

Features

  • Add PSR-14 Events to destination.one import. They allow individual installation to alter the import.

    See psr14 for an overview of PSR-14 Events.

    Added Events:

    • Allow to modify TYPO3 sys_categories before adding them to an event during import.
    • Allow to modify an event object before importing.

  • Add source to events. destination.one provides the original source, either them self or an external. This is now saved in order to make it easier for editors and companies to contact the original source and ask to fix broken data.

Fixes

  • Improve handling of dates with no end. This was always technically possible. Still support from extension was missing. This now got improved, the date object will not throw exceptions due to format() calls on none. Furthermore the PHPDoc now reflects that there might be null instead of \DateTime. Also the setter was adjusted to allow null values.

Tasks

  • Renaming different Destination cases to destination.one throughout documentation and text. Code is left untouched in order to not break things.
  • Migrate away from Extbase Category to custom Category. The extension already provided its own Category model. TYPO3 deprecated and will remove the default Models. We consider this none breaking as this is considered to be internal API.

Deprecation

Nothing