Find a file
Daniel Siepmann 5170c5445b
Improve integration of acceptance tests (#7)
Do not handle necessary processes ourself.
Instead use codeception extension.

Wrap strings in yaml to ensure they are not interpreted as something
else.
2022-10-20 08:45:56 +02:00
.github/workflows [FEATURE] Add JavaScript functionality (#2) 2022-09-28 11:35:07 +02:00
Classes Add form integration (#6) 2022-09-29 08:41:44 +02:00
Configuration Add form integration (#6) 2022-09-29 08:41:44 +02:00
patches [TASK] Kickstart extension with basic features (#1) 2022-09-27 10:35:40 +02:00
Resources Add basic ce setup (#5) 2022-09-28 15:32:26 +02:00
Tests Add form integration (#6) 2022-09-29 08:41:44 +02:00
.gitattributes [FEATURE] Add JavaScript functionality (#2) 2022-09-28 11:35:07 +02:00
.gitignore [FEATURE] Add JavaScript functionality (#2) 2022-09-28 11:35:07 +02:00
.php-cs-fixer.dist.php [TASK] Kickstart extension with basic features (#1) 2022-09-27 10:35:40 +02:00
codeception.dist.yml Improve integration of acceptance tests (#7) 2022-10-20 08:45:56 +02:00
composer.json Add form integration (#6) 2022-09-29 08:41:44 +02:00
ext_localconf.php Add form integration (#6) 2022-09-29 08:41:44 +02:00
phpstan.neon [FEATURE] Add JavaScript functionality (#2) 2022-09-28 11:35:07 +02:00
phpunit.xml.dist [FEATURE] Add JavaScript functionality (#2) 2022-09-28 11:35:07 +02:00
README.rst Add form integration (#6) 2022-09-29 08:41:44 +02:00
shell.nix Improve integration of acceptance tests (#7) 2022-10-20 08:45:56 +02:00

TYPO3 Extension Watchlist

Adds the feature of a watchlist to the frontend of TYPO3 CMS.

Users are able to add "items" to the watchlist. They are also able to remove things from watchlist and show the current watchlist.

Items can be anything. The extension uses interfaces and developers are able to connect whatever they want to be a thing that can be added to the watchlist.

Feature set

The extension provides an controller with actions to add and remove items from watchlist. Each item can only exist once within the watchlist.

There is also an action to show the current watchlist.

The extension ships with support for items of type pages, but this is more a demonstration an used for testing. Projects are way too different and should provide their own items, see "Custom Items".

The extension also provides a JavaScript which will parse data-Attributes of DOM and attach listener to add elements to the watchlist.

Allows to render the items of watchlist within an EXT:form form.

Concept

The extension only provides the functionality, no concrete project specific implementation. It is up to the developer and integrator of the project to provide necessary pieces, see "Custom Items". The extension always only uses identifier of each item and does not know anything else about items.

Custom Items

A developer needs to implement an ItemHandler and an class representing the Item. FormElementAwareItem can optionally be implemented as well, in order to make use of items within an EXT:form form.

The used identifier has to be unique throughout the system. The first part is the item type which is returned by the ItemHandler to be handled, followed by a minus and the rest of the identifier, leading to: <type>-rest-of-identifier.

Commas should not be used within the identifier. The identifiers will be stored in as csv within a cookie.

ItemHandler

The class needs to implement the WerkraumMedia\Watchlist\Domain\ItemHandlerInterface. The purpose is to convert an identifier of that item to an actual instance of that item. The Handler needs to be registered via Symfony Tags, e.g. via Services.yaml:

WerkraumMedia\WatchlistExample\PageItem\ItemHandler:
  tags: ['watchlist.itemHandler']

Item

The class needs to implement the WerkraumMedia\Watchlist\Domain\Model\Item.

FormElementAwareItem

The class can implement the WerkraumMedia\Watchlist\Domain\Model\FormElementAwareItem.

The methods are used by the default EXT:form integration. It is up to the developer + integrator to not use this interface and alter the rendering.

Example

The extension delivers an example implementation for testing purposes, check out:

  • Tests/Fixtures/WatchlistExample/Classes/Domain/Items/Page/ItemHandler.php
  • Tests/Fixtures/WatchlistExample/Classes/Domain/Items/Page/Page.php This implements both Item as well as FormElementAwareItem.
  • Tests/Fixtures/WatchlistExample/Configuration/Services.yaml

The example demonstrates how to fetch information from database, including file references.

EXT:form integration

The provided Configuration needs to be loaded via TypoScript. Use a free identifier:

plugin.tx_form.settings.yamlConfigurations {
    80 = EXT:watchlist/Configuration/Form/Setup.yaml
}

This will register a new form element type Watchlist that can be used like this:

-
  type: Watchlist
  identifier: watchlist-1
  label: 'Watchlist'

A default template is provided which will render all items with checkboxes.

JavaScript

The JavaScript respects two data- attributes:

data-watchlist-counter

Defines that this element will hold the current number of items on watch list. The JavaScript will update the content of the element.

<span data-watchlist-counter class="watchlist-badge-counter"></span>
data-watchlist-item

Defines that this element represents an actual item. The attribute needs the identifier of the item as value, e.g.: data-watchlist-item="page-1"

An EventListener will be added listening for click events on that element. Each click will toggle the state of the item on the watch list.

The JavaScript will add a CSS class to the element, depending on the state of the item. watchlist-inactive will be added in case the item is not on the watchlist. watchlist-active will be added in case the item is on the watchlist.

A custom Event will be triggered whenever an item is added or removed from the watchlist. The event is triggered on the document. The event provides the identifier of the item. An example listener can look like:

document.addEventListener('WatchlistUpdate', function(event) {
    console.log(event.detail.watchlistItem);
});

Example

A concrete example can be found within Tests/Fixtures/FrontendRendering.typoscript. This example includes the provided JavaScript file as well as some custom CSS and Markup. The content element is not necessary.