tilttek / table-safety-bundle
tilttek/table-safety in Symfony: screens where players set lines and veils and raise signals, a game master's screen with live alerts, anonymous by default.
Package info
github.com/TiltTek/table-safety-bundle
Type:symfony-bundle
pkg:composer/tilttek/table-safety-bundle
Requires
- php: >=8.5
- ext-intl: *
- doctrine/dbal: ^4.5
- phil/content-warnings: ^0.1@dev
- phil/content-warnings-bundle: ^0.1@dev
- phil/resource: ^0.1@dev
- psr/clock: ^1.0
- psr/log: ^3.0
- symfony/config: ^8.2
- symfony/dependency-injection: ^8.2
- symfony/form: ^8.2
- symfony/http-foundation: ^8.2
- symfony/http-kernel: ^8.2
- symfony/options-resolver: ^8.2
- symfony/routing: ^8.2
- symfony/security-csrf: ^8.2
- symfony/string: ^8.2
- symfony/translation-contracts: ^3.6
- tilttek/table-safety: ^0.3@dev
- twig/twig: ^3.21
Requires (Dev)
- ext-zlib: *
- doctrine/doctrine-bundle: ^3.3
- doctrine/orm: ^3.7
- phil/paged-media: ^0.1@dev
- phil/privacy-bundle: ^0.1@dev
- phil/ux-kit: ^0.5@dev
- phpunit/phpunit: ^13.4
- symfony/browser-kit: ^8.2
- symfony/clock: ^8.2
- symfony/console: ^8.2
- symfony/css-selector: ^8.2
- symfony/dom-crawler: ^8.2
- symfony/event-dispatcher: ^8.2
- symfony/framework-bundle: ^8.2
- symfony/mercure: ^0.10
- symfony/translation: ^8.2
- symfony/twig-bridge: ^8.2
- symfony/twig-bundle: ^8.2
- symfony/ux-twig-component: ^3.7
- symfony/yaml: ^8.2
Suggests
- doctrine/orm: To add the tables of the safety tools to the schema the ORM generates, and so to the migrations
- phil/paged-media: For the printable cards of a table as a PDF: the X-card, the sheet of the lines and veils and that of the consent checklist
- phil/privacy-bundle: To export and erase a participant's answers, stars and wishes and named signals with the rest of their account
- phil/ux-kit: For the recipes Card, Badge, Button and Alert the screens are built of, through the Symfony UX Toolkit
- symfony/console: For the command that purges the signals older than the retention
- symfony/mercure-bundle: For the hub each signal is pushed to and the authorization cookie of the viewers
- symfony/stimulus-bundle: For the controller that sends the signals in the background and announces each new one
- symfony/ux-twig-component: For the screens, built of the recipes of a kit of the Symfony UX Toolkit
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-11-21 03:06:35 UTC
README
The safety tools of role-playing tables in a Symfony application: the screens where participants answer and raise signals, the game master's screen, and the signals in real time — anonymous by default.
tilttek/table-safety-bundle integrates tilttek/table-safety with Symfony. The tables' settings, the participants'
lines and veils, consent checklists, session zero answers and stars and wishes, and the signals of play are kept in
Doctrine DBAL, in four tables the bundle adds to the schema the ORM generates, so that the application's migrations
create them. The screens — the table during play, a participant's answers, the session zero, the stars and wishes of a
session, the game master's screen — are built of the recipes of a UX Toolkit kit and work without JavaScript: every
signal is a plain form. A Stimulus controller sends the signals in the background, adds each new one as it is raised and
announces it to screen readers. The X-card, the lines and veils and the consent checklist print as blank cards for a
table played in person, as a page or, with phil/paged-media, as a PDF. With a Mercure hub, each signal is pushed to
the private topic of its table — or of its game master, for a discreet signal — with identifiers only. The application
says who takes part in a table and who runs it through one interface; a command purges old signals; and a participant's
answers are exported and erased with their account through phil/privacy-bundle.
It is for a Symfony application that runs tables — a club, a convention, a play-by-post site, a virtual tabletop — and wants their safety tools without exposing who said what. The library alone suits an application without Symfony.
It requires tilttek/table-safety, phil/content-warnings-bundle for the catalogue of themes, Doctrine DBAL, Symfony's
form, HTTP, routing and CSRF components, and Twig; the ORM, the console, the Mercure component, phil/paged-media and
phil/privacy-bundle are optional, and the bundle registers what uses them only when they are installed or configured.
Status
| Part | State |
|---|---|
| Configuration of the stores, the access, the layout, the defaults of a table, the hub and the retention | Implemented and tested |
DbalTableStore, DbalParticipationStore, DbalSignalStore, DbalFeedbackStore and the four tables, with the schema listener |
Implemented and tested |
| The forms of the lines and veils, the checklist, the session zero, the stars and wishes, the tools of an announcement and the settings | Implemented and tested |
| The screens of the table, the answers, the session zero, the stars and wishes and the game master, in English and French | Implemented and tested |
| The routes of the signals: raising, the feed, marking as seen | Implemented and tested |
| The signals pushed to Mercure, and the subscription of each viewer | Implemented and tested |
| The Stimulus controller of the signals | Implemented |
| The printable cards — X-card, lines and veils, consent checklist — as a page and as a PDF | Implemented and tested |
The command tilttek:table-safety:purge-signals |
Implemented and tested |
Export and erasure of a participant for phil/privacy-bundle |
Implemented and tested |
The Symfony Flex recipe, in recipe/ |
Prepared, not published |
Documentation
| Document | What it covers |
|---|---|
| Installation | Requirements, installing, the routes, the tables, the access and the recipe. |
| Configuration | Every option, with an example. |
| Screens | The routes, the templates, the printable cards, the kit's recipes, the forms, the Stimulus controller and accessibility. |
| Real time | The signals pushed to Mercure, the topics and the subscriptions. |
| Database | The four tables and their keys. |
| Upgrading | The migrations an application runs when the tables change. |
| Privacy | What stays anonymous, a participant's export and erasure, and the purge of signals. |
| Extension points | Replacing the access, a store, the catalogue, the templates. |
| Testing | The bundle's tests, and testing an application that uses it. |
| Reference | Every class and service of the bundle. |
Quick start
// config/bundles.php Phil\ContentWarningsBundle\PhilContentWarningsBundle::class => ['all' => true], Tilttek\TableSafetyBundle\TilttekTableSafetyBundle::class => ['all' => true],
# config/packages/tilttek_table_safety.yaml tilttek_table_safety: table_access: App\TableSafety\TableAccess mercure: { hub: mercure.hub.default } # config/routes/tilttek_table_safety.yaml tilttek_table_safety: resource: '@TilttekTableSafetyBundle/config/routes.php'
A participant of table:7 then opens /table-safety/table:7; its game master, /table-safety/table:7/game-master.
Requirements
PHP 8.5 or later with ext-intl, Symfony 8.2, Doctrine DBAL 4.5, Twig 3.21.
Contributing
Contributions are welcome on the PHIL monorepo: read the contribution guide and the code of conduct. Report a vulnerability privately, as the security policy explains, never in a public issue.
License
MIT, © Philippe Gamache, doing business as Le Gnome Archiviste; a Tilttek project. See LICENSE.