Change all content from rst format to markdown and correct spelling/grammar

Remove the label if there is only one scope and no scope picking field is displayed.

Closes #449

See merge request Chill-Projet/chill-bundles!911

.changes/unreleased/DX-20251117-160650.yaml

@@ -0,0 +1,6 @@
+kind: DX
+body: Use mkdocs instead of sphinx to build chill developer documentation
+time: 2025-11-17T16:06:50.46185765+01:00
+custom:
+    Issue: "386"
+    SchemaChange: No schema change

.changes/unreleased/Feature-20251112-103224.yaml

@@ -0,0 +1,6 @@
+kind: Feature
+body: Make a calendar item on the 'mes rendez-vous' page clickable. Clicking will navigate to the edit page of the calendar item.
+time: 2025-11-12T10:32:24.916576945+01:00
+custom:
+    Issue: "461"
+    SchemaChange: No schema change

.changes/unreleased/Fixed-20251112-170025.yaml

@@ -0,0 +1,6 @@
+kind: Fixed
+body: Display calendar items for which an invite was accepted on the mes rendez-vous page
+time: 2025-11-12T17:00:25.58946528+01:00
+custom:
+    Issue: "463"
+    SchemaChange: No schema change

.changes/unreleased/Fixed-20251113-120125.yaml

@@ -0,0 +1,7 @@
+kind: Fixed
+body: |
+    Improve accessibility on login page
+time: 2025-11-13T12:01:25.488478771+01:00
+custom:
+    Issue: ""
+    SchemaChange: No schema change

.changes/unreleased/UX-20251030-153126.yaml

@@ -0,0 +1,6 @@
+kind: UX
+body: Remove the label if there is only one scope and no scope picking field is displayed.
+time: 2025-10-30T15:31:26.807444365+01:00
+custom:
+    Issue: "449"
+    SchemaChange: No schema change

.changes/v3.10.0.md

@@ -0,0 +1,6 @@
+## v3.10.0 - 2025-03-17
+### Feature
+* ([#363](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/363)) Display social actions grouped per social issue within activity form   
+### Fixed
+* ([#362](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/362)) Fix Dependency Injection, which prevented to save the CalendarRange   
+* ([#368](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/368)) fix search query for user groups   

.changes/v3.10.1.md

@@ -0,0 +1,3 @@
+## v3.10.1 - 2025-03-17
+### DX
+* Remove yarn dependency to symfony/ux-translator, to ease the build process

.changes/v3.10.2.md

@@ -0,0 +1,3 @@
+## v3.10.2 - 2025-03-17
+### Fixed
+* Replace a ts-expect-error with a ts-ignore   

.changes/v3.10.3.md

@@ -0,0 +1,3 @@
+## v3.10.3 - 2025-03-18
+### DX
+* Eslint fixes   

.changes/v3.11.0.md

@@ -0,0 +1,19 @@
+## v3.11.0 - 2025-04-17
+### Feature
+* ([#365](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/365)) Add counters of actions and activities, with 2 boxes to (1) show the number of active actions on total actions and (2) show the number of activities in a accompanying period, and pills in menus for showing the number of active actions and the number of activities.
+* ([#364](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/364)) Added a second phone number "telephone2" to the thirdParty entity. Adapted twig templates and vuejs apps to handle this phone number
+
+  **Schema Change**: Add columns or tables
+* Signature: add a button to go directly to the signature zone, even if there is only one
+### Fixed
+* Fixed wrong translations in the on-the-fly for creation of thirdParty
+* Fixed update of phone number in on-the-fly edition of thirdParty
+* Fixed closing of modal when editing thirdParty in accompanying course works
+* Shorten the delay between two execution of AccompanyingPeriodStepChangeCronjob, to ensure at least one execution in a day
+* ([#102](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/102)) Fix display of title in document list
+* When cleaning the old stored object versions, do not throw an error if the stored object is not found on disk
+* Add consistent log prefix and key to logs when stale workflows are automatically canceled
+* ([#380](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/380)) Remove the "not null" validation constraint on recently added properties on HouseholdComposition
+
+### DX
+* Add new chill-col style for displaying title and aside in a flex table

.changes/v3.12.0.md

@@ -0,0 +1,22 @@
+## v3.12.0 - 2025-06-30
+### Feature
+* ([#377](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/377)) Add the document file name to the document title when a user upload a document, unless there is already a document title.   
+* Add desactivation date for social action and issue csv export   
+* Add Emoji and Fullscreen feature to ckeditor configuration   
+* ([#321](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/321)) Create editor which allow us to toggle between rich and simple text editor   
+* Do not remove workflow which are automatically canceled after staling for more than 30 days   
+### Fixed
+* ([#376](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/376)) trying to prevent bug of typeerror in doc-history + improved display of document history   
+* ([#381](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/381)) Display previous participation in acc course work even if the person has left the acc course   
+* ([#372](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/372)) Fix display of text in calendar events   
+* Add missing translation for user_group.no_user_groups   
+* Fix admin entity edit actions for event admin entities and activity reason (category) entities   
+* ([#392](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/392)) Allow null and cast as string to setContent method for NewsItem
+   
+* ([#393](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/393)) Doc Generation: the "dump only" method send the document as an email attachment.   
+### DX
+* ([#352](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/352)) Remove dead code for wopi-link module   
+* Replace library node-sass by sass, and upgrade bootstrap to version 5.3 (yarn upgrade / install is required)   
+### UX
+* ([#374](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/374)) Remove default filter in_progress for the page 'my tasks'; Allows for new tasks to be displayed upon opening of the page   
+* Improve labeling of fields in person resource creation form   

.changes/v3.12.1.md

@@ -0,0 +1,3 @@
+## v3.12.1 - 2025-06-30
+### Fixed
+* Fix loading of the list of documents   

.changes/v3.4.3.md

@@ -0,0 +1,4 @@
+## v3.4.3 - 2024-12-05
+### Fixed
+* Remove the "not null" constraint on person supplementary phones
+* Remove doctrine annotation that prevent from adding documents to activities

.changes/v3.5.0.md

@@ -0,0 +1,6 @@
+## v3.5.0 - 2024-12-09
+### Feature
+* ([#318](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/318)) Show all the pages of the documents in the signature app 
+### Fixed
+* Wrap the signature's change state into a transaction, to avoid race conditions 
+* Fix display of gender label 

.changes/v3.5.1.md

@@ -0,0 +1,4 @@
+## v3.5.1 - 2024-12-16
+### Fixed
+* Filiation: fix the display of the gender label in the graph 
+* Wrap handling of PdfSignedMessage into transactions 

.changes/v3.5.2.md

@@ -0,0 +1,3 @@
+## v3.5.2 - 2024-12-19
+### Fixed
+* ([#345](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/345)) Export: activity filtering of users that were associated to an activity between certain dates. Results contained activities that were not within the specified date range" 

.changes/v3.5.3.md

@@ -0,0 +1,3 @@
+## v3.5.3 - 2025-01-07
+### Fixed
+* Fix the EntityToJsonTransformer to return an empty array if the value is "" 

.changes/v3.6.0.md

@@ -0,0 +1,9 @@
+## v3.6.0 - 2025-01-16
+### Feature
+* Importer for addresses does not fails when the postal code is not found with some addresses, and compute a recap list of all addresses that could not be imported. This recap list can be send by email. 
+* ([#346](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/346)) Create a driver for storing documents on disk (instead of openstack object store)
+ 
+* Add address importer from french Base d'Adresse Nationale (BAN) 
+* ([#343](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/343)) Add csv export for social issues and social actions 
+### Fixed
+* Export: fix missing alias in activity between certain dates filter. Condition added for alias. 

.changes/v3.7.0.md

@@ -0,0 +1,62 @@
+## v3.7.0 - 2025-01-21
+### Feature
+* Use the Notifier component from Symfony to sens short messages (SMS). This allow to use more provider.
+### Fixed
+* ([#348](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/348)) [export] Fix aggregation of referrer's scope and job: fix the date range comparison
+
+### Warning on configuration of Notifier component
+
+If installed in an symfony app where the recipes are activated, this configuration should be added automatically:
+
+```yaml
+framework:
+    notifier:
+        chatter_transports:
+        texter_transports:
+            ovhcloud: '%env(OVHCLOUD_DSN)%'
+        channel_policy:
+            # use chat/slack, chat/telegram, sms/twilio or sms/nexmo
+            urgent: ['email']
+            high: ['email']
+            medium: ['email']
+            low: ['email']
+        admin_recipients:
+            - { email: admin@example.com }
+```
+
+Actually, you should either:
+
+- remove the configuration of ovhcloud added by the recipe
+- or remove the previous configuration of chill, to avoid keeping legacy configuration
+
+#### Remove the added configuration and keep the legacy configuration
+
+To remove the configuration:
+
+```diff
+framework:
+    notifier:
+        chatter_transports:
+        texter_transports:
+-            ovhcloud: '%env(OVHCLOUD_DSN)%'
+```
+
+In that case, the previous configuration, which was stored under the `chill_main.short_messages.dsn` will be reconfigured into the Notifier component's configuration.
+
+#### Properly configure SMS
+
+You can also properly configure it, as [described in the OVH cloud provider repository](https://github.com/symfony/ovh-cloud-notifier/tree/5.4?tab=readme-ov-file#dsn-example) (where the scheme is `ovhcloud`):
+
+**NOTE**: You have access to all notifier available with the [Notifier component](https://symfony.com/doc/current/notifier.html#notifier-sms-channel). You are not restricted to use OVH as a provider.
+
+```diff
+framework:
+    notifier:
+        chatter_transports:
+        texter_transports:
++            ovhcloud: '%env(OVHCLOUD_DSN)%' # this value should be located in a variable, and have `ovhcloud://` as a scheme
+
+chill_main:
+-    short_messages:
+-        dsn: '%env(string:SHORT_MESSAGE_DSN)%'
+```

.changes/v3.7.1.md

@@ -0,0 +1,3 @@
+## v3.7.1 - 2025-01-21
+### Fixed
+* Fix legacy configuration processor for notifier component   

.changes/v3.8.0.md

@@ -0,0 +1,11 @@
+## v3.8.0 - 2025-02-03
+### Feature
+* Improve the UX of the news item admin form to prevent wrong usage
+* ([#319](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/319)) Notification list: display the concerned person's badges in the list
+* ([#320](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/320)) Show the first 3 persons directly in the accompanying period's banner
+* ([#334](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/334)) Suggest current user when creating an activity
+* ([#331](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/331)) Add attachments to workflows
+### Fixed
+* ([#350](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/350)) Add validation error to manual selection of person in PersonDuplicateController
+* ([#354](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/354)) Fix document category creation
+* ([#351](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/351)) Add definitive whitespace between span elements in vue PersonText component

.changes/v3.8.1.md

@@ -0,0 +1,3 @@
+## v3.8.1 - 2025-02-05
+### Fixed
+* Fix household link in the parcours banner   

.changes/v3.8.2.md

@@ -0,0 +1,3 @@
+## v3.8.2 - 2025-02-10
+### Fixed
+* ([#358](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/358)) Remove "filter" button on list of documents in the workflow's "add attachement" modal   

.changes/v3.9.0.md

@@ -0,0 +1,10 @@
+## v3.9.0 - 2025-02-27
+### Feature
+* ([#349](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/349)) Suggest all referrers within actions of the accompanying period when creating an activity   
+* ([#343](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/343)) Add possibility to export a csv with all social issues and social actions   
+* ([#360](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/360)) Restore document to previous kept version when a workflow is canceled   
+* ([#341](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/341)) Add a list of third parties from within the admin (csv download)   
+### Fixed
+* fix generation of document with accompanying period context, and list of activities and works   
+### DX
+* ([#333](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/333)) Create an unique source of trust for translations   

.changes/v3.9.1.md

@@ -0,0 +1,3 @@
+## v3.9.1 - 2025-02-27
+### Fixed
+* Fix post/patch request with missing 'type' property for gender   

.changes/v3.9.2.md

@@ -0,0 +1,3 @@
+## v3.9.2 - 2025-02-27
+### Fixed
+* Use fetchResults method to fetch all social issues instead of only the first page   

.changes/v4.0.0.md

@@ -0,0 +1,74 @@
+## v4.0.0 - 2025-07-08
+### Feature
+* ([#359](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/359)) Allow the merge of two accompanying period works
+### Fixed
+* ([#390](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/390)) Display the list of participant in the results, even if there is only one participant and that the search result display the requestor
+* Fix admin entity edit actions for event admin entities and activity reason (category) entities
+* Fix translations for social action fields in admin form: results, goals, evaluations
+### DX
+* Rewrite exports to run them asynchronously
+
+  **Schema Change**: Add columns or tables
+* Allow TranslatableMessage in flash messages
+### UX
+* Improve labeling of fields in person resource creation form
+
+
+**Release notes**
+
+- Add new methods to serialize data using the rector rule
+- Remove all references to the Request in filters, aggregators, filters. Actually, the most frequent occurence is `$security->getUser()`.
+- Refactor manually the initializeQuery method
+- Remove the injection of ExportManager into the constructor of each export element:
+
+  ```diff
+
+  - class MyFormatter implements FormatterInterface
+  + class MyFormatter implements FormatterInterface, \Chill\MainBundle\Export\ExportManagerAwareInterface
+  {
+  +    use \Chill\MainBundle\Export\Helper\ExportManagerAwareTrait;
+
+  -    public function __construct(private ExportManager $exportmanager) {}
+
+       public function MyMethod(): void
+       {
+  -          $this->exportManager->getFilter('alias');
+  +          $this->getExportManager()->getFilter('alias');
+       }
+  }
+  ```
+- configure messenger to handle export in a queue:
+
+```diff
+# config/packages/messenger.yaml
+framework:
+    messenger:
+        routing:
++            'Chill\MainBundle\Export\Messenger\ExportRequestGenerationMessage': priority
+```
+
+- add missing methods to exports, aggregators, filters, formatter:
+
+  ```php
+  public function normalizeFormData(array $formData): array;
+
+  public function denormalizeFormData(array $formData, int $fromVersion): array;
+  ```
+
+  There are rector rules to generate those methods:
+
+  - `Chill\Utils\Rector\Rector\ChillBundleAddNormalizationMethodsOnExportRector`
+
+  See:
+
+  ```php
+  // upgrade chill exports
+  $rectorConfig->rules([\Chill\Utils\Rector\Rector\ChillBundleAddNormalizationMethodsOnExportRector::class]);
+  ```
+
+  This rule will create most of the work necessary, but some manuals changes are still necessary:
+
+  - we must set manually the correct repository for method `denormalizeDoctrineEntity`;
+  - when the form data contains some entities, and the form type is not one of EntityType::class, PickUserDynamicType::class, PickUserLocationType::class, PickThirdpartyDynamicType::class, Select2CountryType::class, then we must handle the normalization manually (using the `\Chill\MainBundle\Export\ExportDataNormalizerTrait`)
+
+

.changes/v4.0.1.md

@@ -0,0 +1,4 @@
+## v4.0.1 - 2025-07-08
+### Fixed
+* Fix package.json for compilation
+   

.changes/v4.0.2.md

@@ -0,0 +1,4 @@
+## v4.0.2 - 2025-07-09
+### Fixed
+* Fix add missing translation   
+* Fix the transfer of evaluations and documents during of accompanyingperiodwork   

.changes/v4.1.0.md

@@ -0,0 +1,12 @@
+## v4.1.0 - 2025-08-26
+### Feature
+* ([#400](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/400)) Add filter to social actions list to filter out actions where current user intervenes   
+* ([#399](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/399)) Show filters on list pages unfolded by default   
+* Expansion of event module with new fields in the creation form: thematic, internal/external animator, responsable, and budget elements. Filtering options in the event list + adapted exports   
+
+  **Schema Change**: Add columns or tables
+### Fixed
+* ([#382](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/382)) adjust display logic for accompanying period dates, include closing date if period is closed.   
+* ([#384](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/384)) add min and step attributes to integer field in DateIntervalType   
+### UX
+* Limit display of participations in event list   

.changes/v4.2.0.md

@@ -0,0 +1,10 @@
+## v4.2.0 - 2025-09-02
+### Feature
+* ([#64](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/64)) Add external identifier for a Person
+
+  **Schema Change**: Add columns or tables
+* ([#330](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/330) Allow users to choose for which notifications they want to receive an email
+### Fixed
+* ([#422](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/422)) Fixed html layout of pages for recovering password
+* Fix typo in 'uncheckAll' script for centers selection
+* Fix incorrect parameter name in event details link

.changes/v4.2.1.md

@@ -0,0 +1,6 @@
+## v4.2.1 - 2025-09-03
+### Fixed
+* Fix exports to work with DirectExportInterface   
+### DX
+* Improve error message when a stored object cannot be written on local disk
+   

.changes/v4.3.0.md

@@ -0,0 +1,10 @@
+## v4.3.0 - 2025-09-08
+### Feature
+* ([#409](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/409)) Add 45 and 60 min calendar ranges   
+* Add a command to generate a list of permissions   
+* ([#412](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/412)) Add an absence end date   
+
+  **Schema Change**: Add columns or tables
+### Fixed
+* fix date formatting in calendar range display   
+* Change route URL to avoid clash with person duplicate controller method   

.changes/v4.4.0.md

@@ -0,0 +1,8 @@
+## v4.4.0 - 2025-09-11
+### Feature
+* ([#359](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/359)) Allow the merge of two accompanying period works   
+* ([#369](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/369)) Duplication of a document to another accompanying period work evaluation   
+* ([#359](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/359)) Fusion of two accompanying period works   
+### Fixed
+* Fix display of 'duplicate' and 'merge' buttons in CRUD templates   
+* Fix saving notification preferences in user's profile   

.changes/v4.4.1.md

@@ -0,0 +1,3 @@
+## v4.4.1 - 2025-09-11
+### Fixed
+* fix translations in duplicate evaluation document modal and realign close modal button   

.changes/v4.4.2.md

@@ -0,0 +1,3 @@
+## v4.4.2 - 2025-09-12
+### Fixed
+* Fix document generation and workflow generation do not work on accompanying period work documents   

.changes/v4.5.0.md

@@ -0,0 +1,13 @@
+## v4.5.0 - 2025-10-03
+### Feature
+* Only allow delete of attachment on workflows that are not final   
+* Move up signature buttons on index workflow page for easier access   
+* Filter out document from attachment list if it is the same as the workflow document   
+* Block edition on attached document on workflow, if the workflow is finalized or sent external   
+* Convert workflow's attached document to pdf while sending them external   
+* After a signature is canceled or rejected, going to a waiting page until the post-process routines apply a workflow transition   
+### Fixed
+* ([#426](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/426)) Increased the number of required characters when setting a new password in Chill from 9 to 14 - GDPR compliance   
+* Fix permissions on storedObject which are subject by a workflow   
+### DX
+* Introduce a WaitingScreen component to display a waiting screen   

.changes/v4.5.1.md

@@ -0,0 +1,4 @@
+## v4.5.1 - 2025-10-03
+### Fixed
+* Add missing javascript dependency   
+* Add exception handling for conversion of attachment on sending external, when documens are already in pdf   

.changes/v4.6.0.md

@@ -0,0 +1,14 @@
+## v4.6.0 - 2025-10-15
+### Feature
+* ([#423](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/423)) Create environment banner that can be activated and configured depending on the image deployed   
+* ([#394](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/394)) Only show active workflow on the page "my tracked workflow"   
+### Fixed
+* Fix loading of classLists in SocialIssuesAcc.vue, ensure elements are present   
+* Fix the rendering of list of StoredObjectVersions, where there are kept version (before converting to pdf) and intermediate versions deleted   
+* ([#434](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/434)) Notification: fix editing of sent notification by removing form.addressesEmails, a field that no longer exists   
+* Fix loading of social issues and social actions within vue component   
+* ([#446](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/446)) Add unique condition on stored object filename, with cleaning step on existing duplicate filenames   
+
+  **Schema Change**: Drop or rename table or columns, or enforce new constraint that must be manually fixed
+* [workflow] take permissions into account to delete the workflow attachment   
+* ([#448](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/448)) Fix the execution of daily cronjob notification, when the previous last execution storage was invalid   

.changes/v4.6.1.md

@@ -0,0 +1,3 @@
+## v4.6.1 - 2025-10-27
+### Fixed
+* Fix export case where no 'reason' is picked within the PersonHavingActivityBetweenDateFilter.php   

.changes/v4.7.0.md

@@ -0,0 +1,21 @@
+## v4.7.0 - 2025-11-10
+### Feature
+* ([#385](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/385)) Create invitation list in user menu   
+* ([#404](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/404)) Add columns for comments linked to an activity in the activity list export   
+### Fixed
+* ([#451](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/451)) Fix: display also social actions linked to parents of the selected social issue   
+* ([#453](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/453)) Fix: export actions and their results in csv even when action does not have any goals attached to it.   
+* Fix the possibility to delete a workflow   
+
+  **Schema Change**: Drop or rename table or columns, or enforce new constraint that must be manually fixed
+* ([#457](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/457)) Fix the fusion of thirdparty properties that are located in another schema than public for TO_ONE relations + add extra loop for MANY_TO_MANY relations where thirdparty is the source instead of the target   
+* ([#428](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/428)) Fix suggestion of referrer when creating notification for accompanyingPeriodWorkDocument   
+### DX
+* Send notifications log to dedicated channel, if it exists
+   
+### UX
+* ([#425](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/425)) Change the terms 'cercle' and 'centre' to 'service', and 'territoire' respectively.   
+* ([#542](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/542)) Improve the ux for selecting whether user wants to be notified of the final step of a workflow or all steps   
+* Expand timeSpent choices for evaluation document and translate them to user locale or fallback 'fr'   
+* ([#455](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/455)) Change the order of display for results and objectives in the social work/action form   
+* Wrap text when it is too long within badges   

.changie.yaml

@@ -7,15 +7,29 @@ versionFormat: '## {{.Version}} - {{.Time.Format "2006-01-02"}}'
 kindFormat: '### {{.Kind}}'
 # Note: it is possible to add a `.custom.Long` text manually into the yaml file produced by `changie new`. This will add a long description.
 changeFormat: >-
-    * {{ if not (eq .Custom.Issue "") }}([#{{ .Custom.Issue }}](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/{{ .Custom.Issue }})) {{ end }}{{.Body}} {{ if and (.Custom.Long) (not (eq .Custom.Long "")) }}
+    * {{ if not (eq .Custom.Issue "") }}([#{{ .Custom.Issue }}](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/{{ .Custom.Issue }})) {{ end }}{{ .Body }}   {{ if and .Custom.SchemaChange (ne .Custom.SchemaChange "No schema change") }}
+
+      **Schema Change**: {{ .Custom.SchemaChange }}
+      {{- end -}}
+
+    {{ if and (.Custom.Long) (not (eq .Custom.Long "")) }}{{ .Custom.Long }}{{ end }}
 
-      {{ .Custom.Long }}{{ end }}
 custom:
+    - key: SchemaChange
+      label: Is a schema change required?
+      optional: false
+      type: enum
+      enumOptions:
+          - "No schema change"
+          - "Add columns or tables"
+          - "Drop or rename table or columns, or enforce new constraint that must be manually fixed"
+
     -   key: Issue
         label: Issue number (on chill-bundles repository) (optional)
         optional: true
         type: int
         minInt: 1
+
 body:
     # allow multiline messages
     block: true

.env

@@ -88,3 +88,7 @@ REDIS_HOST=redis
 REDIS_PORT=6379
 REDIS_URL=redis://${REDIS_HOST}:${REDIS_PORT}
 ###< chill-project/chill-bundles ###
+
+###> symfony/ovh-cloud-notifier ###
+# OVHCLOUD_DSN=ovhcloud://APPLICATION_KEY:APPLICATION_SECRET@default?consumer_key=CONSUMER_KEY&service_name=SERVICE_NAME
+###< symfony/ovh-cloud-notifier ###

.gitignore

@@ -5,16 +5,22 @@ composer.lock
 docs/build/
 .php_cs.cache
 .cache/*
+yarn.lock
 
 docker/db/data
 docker/rabbitmq/data
 
 # in this development bundle, we want to ignore directories related to a real app
 assets/*
+!assets/translator.ts
+!assets/ux-translator
 migrations/*
 templates/*
 translations/*
 
+# we allow developers to add customization on their installation, without commiting it
+config/packages/dev/*
+
 ###> symfony/framework-bundle ###
 /.env.local
 /.env.local.php
@@ -51,3 +57,8 @@ phpstan.neon
 npm-debug.log
 yarn-error.log
 ###< symfony/webpack-encore-bundle ###
+
+###> friendsofphp/php-cs-fixer ###
+/.php-cs-fixer.php
+/.php-cs-fixer.cache
+###< friendsofphp/php-cs-fixer ###

.gitlab-ci.yml

@@ -5,6 +5,7 @@ cache:
     paths:
         - /vendor/
         - .cache
+        - node_modules/
 
 # Bring in any services we need http://docs.gitlab.com/ee/ci/docker/using_docker_images.html#what-is-a-service
 # See http://docs.gitlab.com/ee/ci/services/README.html for examples.
@@ -45,7 +46,7 @@ stages:
 
 build:
     stage: Composer install
-    image: gitea.champs-libres.be/chill-project/chill-skeleton-basic/base-image:php82
+    image: chill/base-image:8.3-edge
     before_script:
         - composer config -g cache-dir "$(pwd)/.cache"
     script:
@@ -60,7 +61,7 @@ build:
 
 code_style:
     stage: Tests
-    image: gitea.champs-libres.be/chill-project/chill-skeleton-basic/base-image:php82
+    image: chill/base-image:8.3-edge
     script:
         - php-cs-fixer fix --dry-run -v --show-progress=none
     cache:
@@ -73,7 +74,7 @@ code_style:
 
 phpstan_tests:
     stage: Tests
-    image: gitea.champs-libres.be/chill-project/chill-skeleton-basic/base-image:php82
+    image: chill/base-image:8.3-edge
     variables:
         COMPOSER_MEMORY_LIMIT: 3G
     before_script:
@@ -90,7 +91,7 @@ phpstan_tests:
 
 rector_tests:
     stage: Tests
-    image: gitea.champs-libres.be/chill-project/chill-skeleton-basic/base-image:php82
+    image: chill/base-image:8.3-edge
     before_script:
         - bin/console cache:clear --env=dev
     script:
@@ -103,9 +104,35 @@ rector_tests:
         paths:
             - vendor/
 
+lint:
+    stage: Tests
+    image: node:20-alpine
+    before_script:
+        - apk add --no-cache python3 make g++ py3-setuptools
+        - export PYTHON="$(which python3)"
+        - export PATH="./node_modules/.bin:$PATH"
+    script:
+        - yarn install --ignore-optional
+        - npx eslint-baseline "src/**/*.{js,ts,vue}"
+    cache:
+        paths:
+            - node_modules/
+
+# psalm_tests:
+#     stage: Tests
+#     image: gitea.champs-libres.be/chill-project/chill-skeleton-basic/base-image:php82
+#     script:
+#         - bin/psalm
+#     allow_failure: true
+#     artifacts:
+#         expire_in: 30 min
+#         paths:
+#             - bin
+#             - tests/app/vendor/
+
 unit_tests:
     stage: Tests
-    image: gitea.champs-libres.be/chill-project/chill-skeleton-basic/base-image:php82
+    image: chill/base-image:8.3-edge
     variables:
         COMPOSER_MEMORY_LIMIT: 3G
     before_script:

.junie/guidelines.md

@@ -0,0 +1,391 @@
+# Project Guidelines for Junie
+
+## Project Overview
+
+Chill is a comprehensive web application built as a set of Symfony bundles. It is a case management system, for social work. The project consists of multiple specialized bundles that provide different functionalities:
+
+- **ChillMainBundle**: Core bundles that provide the foundation of the application
+- **ChillPersonBundle**: Core bundles that provide the foundation of the bundles associated to person (which is the case for all other bundles)
+- **ChillCalendarBundle**: Calendar and scheduling functionality
+- **ChillDocStoreBundle** and **ChillDocGeneratorBundle**: Document management and generation
+- **ChillActivityBundle**, **ChillEventBundle**, **ChillTaskBundle**: Activity and task tracking
+- **ChillBudgetBundle**: Financial management
+- **ChillThirdPartyBundle**: Integration with external systems
+- **ChillCustomFieldsBundle**: Extensibility through custom fields
+- **ChillReportBundle**: Save arbitrary reports about persons
+- **ChillTicketBundle**: Record and track issues about persons
+
+- And several other specialized bundles
+
+## Technology Stack
+
+- **Backend**: PHP 8.3+, Symfony 5.4
+- **Frontend**: JavaScript/TypeScript, Vue.js 3, Bootstrap 5
+- **Build Tools**: Webpack Encore, Yarn
+- **Database**: PostgreSQL with materialized views. We do not support other databases.
+- **Other Services**: Redis, AMQP (RabbitMQ), SMTP
+
+## Project Structure
+
+Note: This is a project that's existed for a long time, and throughout the years we've used multiple structures inside each bundle. When having the choice, the developers should choose the new structure.
+
+The project follows a standard Symfony bundle structure:
+- `/src/Bundle/`: Contains all the Chill bundles. The code is either at the root of the bundle directory, or within a `src/` directory (preferred). See psr4 mapping at the root's `composer.json`.
+- each bundle comes with its own tests, either in the `Tests` directory (when the code is directly within the bundle directory (for instance `src/Bundle/ChillMainBundle/Tests`, `src/Bundle/ChillPersonBundle/Tests`)), or inside the `tests` directory, alongside the `src/` sub-directory (example: `src/Bundle/ChillWopiBundle/tests`) (this is the preferred way).
+- `/docs/`: Contains project documentation
+
+Each bundle typically has the following structure:
+
+- `Controller/`: Contains controllers
+- `Entity/`: Contains Doctrine entities
+- `Repository/`: Contains Doctrine repositories
+- `Resources/`: Contains views, translations, and public assets
+- `DependencyInjection/`: Contains service configuration
+- `Export/`: Contains services related to exports
+- `Security/`: Contains services related to security. Most of the time, those are new voters, and so on.
+
+### A special word about TicketBundle
+
+The ticket bundle is developed using a kind of "Command" pattern. The controller fills a "Command," and a "CommandHandler" handles this command. They are saved in the `src/Bundle/ChillTicketBundle/src/Action` directory.
+
+## Development Guidelines
+
+### Building and Configuration Instructions
+
+All the commands should be run through the `symfony` command, which will configure the required variables.
+
+For assets, we must ensure that we use node at version `^20.0.0`. This is done using `nvm use 20`.
+
+#### Initial Setup
+
+1. **Clone the Repository**:
+   ```bash
+   git clone <repository-url>
+   cd chill-bundles
+   ```
+
+2. **Install PHP Dependencies**:
+   ```bash
+   composer install
+   ```
+
+3. **Install JavaScript Dependencies**:
+   ```bash
+   nvm use 20
+   yarn install
+   ```
+
+4. **Configure Environment Variables**:
+
+   - Create a `.env.local` file with minimal configuration
+   ```bash
+   echo "APP_ENV=dev" >> .env.local
+   ```
+
+5. Start the associated services (database, and so on):
+   ```bash
+   docker compose up -d
+   ```
+
+6. **Set Up the Database**:
+   ```bash
+   # Create the database
+   symfony console doctrine:database:create
+
+   # Run migrations
+   symfony console doctrine:migrations:migrate
+
+   # Load fixtures (optional)
+   symfony console doctrine:fixtures:load
+   ```
+
+7. **Build Assets**:
+   ```bash
+   nvm use 20
+   yarn run encore dev
+   ```
+
+8. **Start the Development Server**:
+   ```bash
+   symfony server:start -d
+   ```
+
+#### Docker Setup
+
+The project includes a Docker configuration for easier development:
+
+1. **Start Docker Services**:
+   ```bash
+   docker-compose up -d
+   ```
+
+2. **Access the Application**:
+   - The application will be available at `http://localhost:8000`
+   - PostgreSQL will be available at `localhost:5432`
+   - Redis will be available at `localhost:6379`
+
+#### Building Assets
+
+Before submitting any changes, you should build the project to ensure that all assets are properly compiled:
+
+```bash
+# For production
+yarn run encore production
+
+# For development with hot-reloading
+yarn run encore dev --watch
+
+# for development
+yarn run encore dev
+```
+
+#### Configuration Files
+
+Key configuration files:
+
+- `config/packages/*.yaml`: Symfony bundle configurations
+- `webpack.config.js`: Webpack Encore configuration
+- `composer.json`: PHP dependencies and scripts
+- `package.json`: JavaScript dependencies and scripts
+- `.env`: Default environment variables. Must usually not be updated: use `.env.local` instead.
+
+### Database migrations
+
+Each time a doctrine entity is created, we generate migration to adapt the database.
+
+The migration is created using the command `symfony console doctrine:migrations:diff --no-interaction --namespace <namespace>`, where the namespace is the relevant namespace for migration. As this is a bash script, remember to quote the `\` (`\` must become `\\` in your command).
+
+Each bundle has his own namespace for migration (always ask me to confirm that command with a list of updated / created entities so that I can confirm to you that it is ok):
+
+- `Chill\Bundle\ActivityBundle` writes migrations to `Chill\Migrations\Activity`;
+- `Chill\Bundle\BudgetBundle` writes migrations to `Chill\Migrations\Budget`;
+- `Chill\Bundle\CustomFieldsBundle` writes migrations to `Chill\Migrations\CustomFields`;
+- `Chill\Bundle\DocGeneratorBundle` writes migrations to `Chill\Migrations\DocGenerator`;
+- `Chill\Bundle\DocStoreBundle` writes migrations to `Chill\Migrations\DocStore`;
+- `Chill\Bundle\EventBundle` writes migrations to `Chill\Migrations\Event`;
+- `Chill\Bundle\CalendarBundle` writes migrations to `Chill\Migrations\Calendar`;
+- `Chill\Bundle\FamilyMembersBundle` writes migrations to `Chill\Migrations\FamilyMembers`;
+- `Chill\Bundle\FranceTravailApiBundle` writes migrations to `Chill\Migrations\FranceTravailApi`;
+- `Chill\Bundle\JobBundle` writes migrations to `Chill\Migrations\Job`;
+- `Chill\Bundle\MainBundle` writes migrations to `Chill\Migrations\Main`;
+- `Chill\Bundle\PersonBundle` writes migrations to `Chill\Migrations\Person`;
+- `Chill\Bundle\ReportBundle` writes migrations to `Chill\Migrations\Report`;
+- `Chill\Bundle\TaskBundle` writes migrations to `Chill\Migrations\Task`;
+- `Chill\Bundle\ThirdPartyBundle` writes migrations to `Chill\Migrations\ThirdParty`;
+- `Chill\Bundle\TicketBundle` writes migrations to `Chill\Migrations\Ticket`;
+- `Chill\Bundle\WopiBundle` writes migrations to `Chill\Migrations\Wopi`;
+
+Once created the, comment's classes should be removed and a description of the changes made to the entities should be added to the migrations, using the `getDescription` method. The migration should not be cleaned by any artificial intelligence, as modifying this migration is error prone.
+
+### Guidelines related to code structure and requirements
+
+#### Usage of clock
+
+When we need to use a DateTime or DateTimeImmutable that need to express "now", we prefer the usage of
+`Symfony\Component\Clock\ClockInterface`, where possible. This is usually not possible in doctrine entities,
+where injection does not work when restoring an entity from a database, but usually possible in services.
+
+In test, we use `\Symfony\Component\Clock\MockClock` which is an implementation of `Symfony\Component\Clock\ClockInterface`
+where we have full and easy control of the date.
+
+### Testing Information
+
+The project uses PHPUnit for testing. Each bundle has its own test suite, and there's also a global test suite at the root level.
+
+#### Use of mock in tests
+
+##### General mocking
+
+For creating mock, we prefer using prophecy (library phpspec/prophecy).
+
+##### Useful helpers and tips that avoid creating a mock
+
+Some notable implementations that are test helpers and avoid creating a mock:
+
+- `\Psr\Log\NullLogger`, an implementation of `\Psr\Log\LoggerInterface`;
+- `\Symfony\Component\Clock\MockClock`, an implementation of `Symfony\Component\Clock\ClockInterface` (already mentioned above);
+- `\Symfony\Component\HttpClient\MockHttpClient`, an implementation of `\Symfony\Contracts\HttpClient\HttpClientInterface`;
+- When using `\Symfony\Component\Mailer\MailerInterface`, we can create the mock with "InMemoryTransport":
+
+    ```php
+    use Symfony\Component\Mailer\Transport\InMemoryTransport;
+    use \Symfony\Component\Mailer\Mailer;
+
+    $transport = new InMemoryTransport();
+    $mailer = new Mailer($transport);
+
+    // After sending:
+    $messages = $transport->getSent(); // array of SentMessage
+    ```
+- When using `\Symfony\Contracts\EventDispatcher\EventDispatcherInterface`, we can use directly an instance of `\Symfony\Component\EventDispatcher\EventDispatcher`;
+
+##### When we prefer not creating a mock
+
+- When we use Doctrine Entities related to the project, we prefer not to use a mock: we instantiate them directly (unless it requires too much code to write);
+
+##### Mocking final and readonly classes
+
+Classes marked as final can't be mocked. To avoid that, either:
+
+- we remove the `final` keyword from the class;
+- we extract an interface from the final class.
+
+This must be a decision made by a human, not by an AI. Every AI task must abort with an explicit message in that case.
+
+#### Running Tests
+
+The tests are run from the project's root (not from the bundle's root).
+
+```bash
+# Run all tests
+vendor/bin/phpunit
+
+# Run a specific test file
+vendor/bin/phpunit path/to/TestFile.php
+
+# Run a specific test method
+vendor/bin/phpunit --filter methodName path/to/TestFile.php
+```
+
+When writing tests, only test specific files. Do not run all tests or the full
+test suite.
+
+#### Test Structure
+
+Tests are organized by bundle and follow the same structure as the bundle itself:
+
+- Unit tests: Test individual components in isolation
+- Integration tests: Test components working together
+- Functional tests: Test the application from the user's perspective
+
+#### Writing Tests
+
+Tests should be placed in the appropriate bundle's test directory. For example, tests for the TicketBundle should be placed in `src/Bundle/ChillTicketBundle/tests/`.
+
+Here's an example of a simple entity test:
+
+```php
+<?php
+
+namespace Chill\TicketBundle\Tests\Entity;
+
+use Chill\TicketBundle\Entity\Ticket;
+use PHPUnit\Framework\TestCase;
+
+class TicketTest extends TestCase
+{
+    public function testGetAndSetExternalRef(): void
+    {
+        $ticket = new Ticket();
+        $externalRef = 'REF-123';
+
+        // Set the external reference
+        $ticket->setExternalRef($externalRef);
+
+        // Verify that getExternalRef returns the correct value
+        self::assertSame($externalRef, $ticket->getExternalRef());
+
+        // Change the external reference
+        $newExternalRef = 'REF-456';
+        $ticket->setExternalRef($newExternalRef);
+
+        // Verify that getExternalRef returns the updated value
+        self::assertSame($newExternalRef, $ticket->getExternalRef());
+    }
+}
+```
+
+#### Test Database
+
+For tests that require a database, the project uses a postgresql database filled with fixtures (usage of doctrine-fixtures). You can configure a different database for testing in the `.env.test` file.
+
+### Code Quality Tools
+
+The project uses several tools to maintain code quality:
+
+#### PHP Code Style
+
+The project uses PHP-CS-Fixer for code style. You can run it with:
+
+```bash
+# Using the composer script
+composer php-cs-fixer
+
+# Or directly
+php-cs-fixer fix --config=./.php-cs-fixer.dist.php
+```
+
+#### Static Analysis
+
+The project uses PHPStan for static analysis. You can run it with:
+
+```bash
+# Using the composer script
+composer phpstan
+
+# Or directly
+vendor/bin/phpstan analyse
+```
+
+#### Automated Refactoring
+
+The project uses Rector for automated refactoring. You can run it with:
+
+```bash
+# Using the composer script
+composer rector
+
+# Or directly
+vendor/bin/rector
+```
+
+#### JavaScript/TypeScript Linting
+
+The project uses ESLint for JavaScript/TypeScript code quality. You can run it with:
+
+```bash
+yarn run eslint
+```
+
+## Deployment
+
+The project can be deployed in a production environment following Symfony's deployment guidelines. The documentation provides detailed instructions for setting up a production environment.
+
+### Production Deployment Checklist
+
+1. Set environment variables for production
+2. Optimize Composer autoloader: `composer install --no-dev --optimize-autoloader`
+3. Compile assets for production: `yarn run encore production`
+4. Clear and warm up the cache: `php bin/console cache:clear --env=prod`
+5. Run database migrations: `php bin/console doctrine:migrations:migrate --env=prod`
+
+## Documentation
+
+Comprehensive documentation is available in the `/docs/` directory, including installation instructions, configuration guides, and operational procedures.
+
+## Development Workflow
+
+1. **Create a Feature Branch**: Always create a new branch for your feature or bugfix
+2. **Write Tests**: Write tests for your changes before implementing them
+3. **Implement Changes**: Implement your changes following the project's coding standards
+4. **Run Tests**: Make sure all tests pass
+5. **Run Code Quality Tools**: Make sure your code passes all code quality checks
+6. **Submit a Pull Request**: Submit a pull request for review
+
+## Debugging
+
+The project includes several tools for debugging:
+
+- **Symfony Profiler**: Available in development mode at `/_profiler`
+- **Xdebug**: Configure your IDE to use Xdebug for step-by-step debugging
+- **Symfony Debug Toolbar**: Available at the bottom of the page in development mode
+
+## Conclusion
+
+When working with this project, Junie should:
+
+1. Understand the modular bundle structure and how the different components interact
+2. Build the project before submitting changes to ensure assets are properly compiled
+3. Run relevant tests to ensure changes don't break existing functionality
+4. Follow the established code style and patterns
+5. Use the provided tools for debugging and code quality

.php-cs-fixer.dist.php

@@ -25,7 +25,7 @@ $config = new PhpCsFixer\Config();
 $config
     ->setFinder($finder)
     ->setRiskyAllowed(true)
-    ->setCacheFile('.cache/php-cs-fixer.cache')
+    ->setCacheFile('var/php-cs-fixer.cache')
     ->setUsingCache(true)
     ->setParallelConfig(PhpCsFixer\Runner\Parallel\ParallelConfigFactory::detect())
 ;

CHANGELOG.md

@@ -6,6 +6,417 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
 
+## v4.7.0 - 2025-11-10
+### Feature
+* ([#385](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/385)) Create invitation list in user menu   
+* ([#404](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/404)) Add columns for comments linked to an activity in the activity list export   
+### Fixed
+* ([#451](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/451)) Fix: display also social actions linked to parents of the selected social issue   
+* ([#453](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/453)) Fix: export actions and their results in csv even when action does not have any goals attached to it.   
+* Fix the possibility to delete a workflow   
+
+  **Schema Change**: Drop or rename table or columns, or enforce new constraint that must be manually fixed
+* ([#457](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/457)) Fix the fusion of thirdparty properties that are located in another schema than public for TO_ONE relations + add extra loop for MANY_TO_MANY relations where thirdparty is the source instead of the target   
+* ([#428](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/428)) Fix suggestion of referrer when creating notification for accompanyingPeriodWorkDocument   
+### DX
+* Send notifications log to dedicated channel, if it exists
+   
+### UX
+* ([#425](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/425)) Change the terms 'cercle' and 'centre' to 'service', and 'territoire' respectively.   
+* ([#542](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/542)) Improve the ux for selecting whether user wants to be notified of the final step of a workflow or all steps   
+* Expand timeSpent choices for evaluation document and translate them to user locale or fallback 'fr'   
+* ([#455](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/455)) Change the order of display for results and objectives in the social work/action form   
+* Wrap text when it is too long within badges   
+
+## v4.6.1 - 2025-10-27
+### Fixed
+* Fix export case where no 'reason' is picked within the PersonHavingActivityBetweenDateFilter.php   
+
+## v4.6.0 - 2025-10-15
+### Feature
+* ([#423](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/423)) Create environment banner that can be activated and configured depending on the image deployed   
+* ([#394](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/394)) Only show active workflow on the page "my tracked workflow"   
+### Fixed
+* Fix loading of classLists in SocialIssuesAcc.vue, ensure elements are present   
+* Fix the rendering of list of StoredObjectVersions, where there are kept version (before converting to pdf) and intermediate versions deleted   
+* ([#434](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/434)) Notification: fix editing of sent notification by removing form.addressesEmails, a field that no longer exists   
+* Fix loading of social issues and social actions within vue component   
+* ([#446](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/446)) Add unique condition on stored object filename, with cleaning step on existing duplicate filenames   
+
+  **Schema Change**: Drop or rename table or columns, or enforce new constraint that must be manually fixed
+* [workflow] take permissions into account to delete the workflow attachment   
+* ([#448](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/448)) Fix the execution of daily cronjob notification, when the previous last execution storage was invalid   
+
+## v4.5.1 - 2025-10-03
+### Fixed
+* Add missing javascript dependency   
+* Add exception handling for conversion of attachment on sending external, when documens are already in pdf   
+
+## v4.5.0 - 2025-10-03
+### Feature
+* Only allow delete of attachment on workflows that are not final   
+* Move up signature buttons on index workflow page for easier access   
+* Filter out document from attachment list if it is the same as the workflow document   
+* Block edition on attached document on workflow, if the workflow is finalized or sent external   
+* Convert workflow's attached document to pdf while sending them external   
+* After a signature is canceled or rejected, going to a waiting page until the post-process routines apply a workflow transition   
+### Fixed
+* ([#426](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/426)) Increased the number of required characters when setting a new password in Chill from 9 to 14 - GDPR compliance   
+* Fix permissions on storedObject which are subject by a workflow   
+### DX
+* Introduce a WaitingScreen component to display a waiting screen   
+
+## v4.4.2 - 2025-09-12
+### Fixed
+* Fix document generation and workflow generation do not work on accompanying period work documents   
+
+## v4.4.1 - 2025-09-11
+### Fixed
+* fix translations in duplicate evaluation document modal and realign close modal button   
+
+## v4.4.0 - 2025-09-11
+### Feature
+* ([#359](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/359)) Allow the merge of two accompanying period works   
+* ([#369](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/369)) Duplication of a document to another accompanying period work evaluation   
+* ([#359](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/359)) Fusion of two accompanying period works   
+### Fixed
+* Fix display of 'duplicate' and 'merge' buttons in CRUD templates   
+* Fix saving notification preferences in user's profile   
+
+## v4.3.0 - 2025-09-08
+### Feature
+* ([#409](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/409)) Add 45 and 60 min calendar ranges   
+* Add a command to generate a list of permissions   
+* ([#412](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/412)) Add an absence end date   
+
+  **Schema Change**: Add columns or tables
+### Fixed
+* fix date formatting in calendar range display   
+* Change route URL to avoid clash with person duplicate controller method   
+
+## v4.2.1 - 2025-09-03
+### Fixed
+* Fix exports to work with DirectExportInterface   
+### DX
+* Improve error message when a stored object cannot be written on local disk
+   
+
+## v4.2.0 - 2025-09-02
+### Feature
+* ([#64](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/64)) Add external identifier for a Person
+
+  **Schema Change**: Add columns or tables
+* ([#330](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/330) Allow users to choose for which notifications they want to receive an email
+### Fixed
+* ([#422](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/422)) Fixed html layout of pages for recovering password
+* Fix typo in 'uncheckAll' script for centers selection
+* Fix incorrect parameter name in event details link
+
+## v4.1.0 - 2025-08-26
+### Feature
+* ([#400](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/400)) Add filter to social actions list to filter out actions where current user intervenes   
+* ([#399](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/399)) Show filters on list pages unfolded by default   
+* Expansion of event module with new fields in the creation form: thematic, internal/external animator, responsable, and budget elements. Filtering options in the event list + adapted exports   
+
+  **Schema Change**: Add columns or tables
+### Fixed
+* ([#382](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/382)) adjust display logic for accompanying period dates, include closing date if period is closed.   
+* ([#384](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/384)) add min and step attributes to integer field in DateIntervalType   
+### UX
+* Limit display of participations in event list   
+
+## v4.0.2 - 2025-07-09
+### Fixed
+* Fix add missing translation   
+* Fix the transfer of evaluations and documents during of accompanyingperiodwork   
+
+## v4.0.1 - 2025-07-08
+### Fixed
+* Fix package.json for compilation
+   
+
+## v4.0.0 - 2025-07-08
+### Feature
+* ([#359](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/359)) Allow the merge of two accompanying period works
+### Fixed
+* ([#390](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/390)) Display the list of participant in the results, even if there is only one participant and that the search result display the requestor
+* Fix admin entity edit actions for event admin entities and activity reason (category) entities
+* Fix translations for social action fields in admin form: results, goals, evaluations
+### DX
+* Rewrite exports to run them asynchronously
+
+  **Schema Change**: Add columns or tables
+* Allow TranslatableMessage in flash messages
+### UX
+* Improve labeling of fields in person resource creation form
+
+
+**Release notes**
+
+- Add new methods to serialize data using the rector rule
+- Remove all references to the Request in filters, aggregators, filters. Actually, the most frequent occurence is `$security->getUser()`.
+- Refactor manually the initializeQuery method
+- Remove the injection of ExportManager into the constructor of each export element:
+
+  ```diff
+
+  - class MyFormatter implements FormatterInterface
+  + class MyFormatter implements FormatterInterface, \Chill\MainBundle\Export\ExportManagerAwareInterface
+  {
+  +    use \Chill\MainBundle\Export\Helper\ExportManagerAwareTrait;
+
+  -    public function __construct(private ExportManager $exportmanager) {}
+
+       public function MyMethod(): void
+       {
+  -          $this->exportManager->getFilter('alias');
+  +          $this->getExportManager()->getFilter('alias');
+       }
+  }
+  ```
+- configure messenger to handle export in a queue:
+
+```diff
+# config/packages/messenger.yaml
+framework:
+    messenger:
+        routing:
++            'Chill\MainBundle\Export\Messenger\ExportRequestGenerationMessage': priority
+```
+
+- add missing methods to exports, aggregators, filters, formatter:
+
+  ```php
+  public function normalizeFormData(array $formData): array;
+
+  public function denormalizeFormData(array $formData, int $fromVersion): array;
+  ```
+
+  There are rector rules to generate those methods:
+
+  - `Chill\Utils\Rector\Rector\ChillBundleAddNormalizationMethodsOnExportRector`
+
+  See:
+
+  ```php
+  // upgrade chill exports
+  $rectorConfig->rules([\Chill\Utils\Rector\Rector\ChillBundleAddNormalizationMethodsOnExportRector::class]);
+  ```
+
+  This rule will create most of the work necessary, but some manuals changes are still necessary:
+
+  - we must set manually the correct repository for method `denormalizeDoctrineEntity`;
+  - when the form data contains some entities, and the form type is not one of EntityType::class, PickUserDynamicType::class, PickUserLocationType::class, PickThirdpartyDynamicType::class, Select2CountryType::class, then we must handle the normalization manually (using the `\Chill\MainBundle\Export\ExportDataNormalizerTrait`)
+
+
+
+## v3.12.1 - 2025-06-30
+### Fixed
+* Fix loading of the list of documents   
+
+## v3.12.0 - 2025-06-30
+### Feature
+* ([#377](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/377)) Add the document file name to the document title when a user upload a document, unless there is already a document title.   
+* Add desactivation date for social action and issue csv export   
+* Add Emoji and Fullscreen feature to ckeditor configuration   
+* ([#321](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/321)) Create editor which allow us to toggle between rich and simple text editor   
+* Do not remove workflow which are automatically canceled after staling for more than 30 days   
+### Fixed
+* ([#376](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/376)) trying to prevent bug of typeerror in doc-history + improved display of document history   
+* ([#381](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/381)) Display previous participation in acc course work even if the person has left the acc course   
+* ([#372](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/372)) Fix display of text in calendar events   
+* Add missing translation for user_group.no_user_groups   
+* Fix admin entity edit actions for event admin entities and activity reason (category) entities   
+* ([#392](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/392)) Allow null and cast as string to setContent method for NewsItem
+   
+* ([#393](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/393)) Doc Generation: the "dump only" method send the document as an email attachment.   
+### DX
+* ([#352](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/352)) Remove dead code for wopi-link module   
+* Replace library node-sass by sass, and upgrade bootstrap to version 5.3 (yarn upgrade / install is required)   
+### UX
+* ([#374](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/374)) Remove default filter in_progress for the page 'my tasks'; Allows for new tasks to be displayed upon opening of the page   
+* Improve labeling of fields in person resource creation form   
+
+## v3.11.0 - 2025-04-17
+### Feature
+* ([#365](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/365)) Add counters of actions and activities, with 2 boxes to (1) show the number of active actions on total actions and (2) show the number of activities in a accompanying period, and pills in menus for showing the number of active actions and the number of activities.
+* ([#364](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/364)) Added a second phone number "telephone2" to the thirdParty entity. Adapted twig templates and vuejs apps to handle this phone number
+
+  **Schema Change**: Add columns or tables
+* Signature: add a button to go directly to the signature zone, even if there is only one
+### Fixed
+* Fixed wrong translations in the on-the-fly for creation of thirdParty
+* Fixed update of phone number in on-the-fly edition of thirdParty
+* Fixed closing of modal when editing thirdParty in accompanying course works
+* Shorten the delay between two execution of AccompanyingPeriodStepChangeCronjob, to ensure at least one execution in a day
+* ([#102](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/102)) Fix display of title in document list
+* When cleaning the old stored object versions, do not throw an error if the stored object is not found on disk
+* Add consistent log prefix and key to logs when stale workflows are automatically canceled
+* ([#380](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/380)) Remove the "not null" validation constraint on recently added properties on HouseholdComposition
+
+### DX
+* Add new chill-col style for displaying title and aside in a flex table
+
+## v3.10.3 - 2025-03-18
+### DX
+* Eslint fixes   
+
+## v3.10.2 - 2025-03-17
+### Fixed
+* Replace a ts-expect-error with a ts-ignore   
+
+## v3.10.1 - 2025-03-17
+### DX
+* Remove yarn dependency to symfony/ux-translator, to ease the build process
+
+## v3.10.0 - 2025-03-17
+### Feature
+* ([#363](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/363)) Display social actions grouped per social issue within activity form   
+### Fixed
+* ([#362](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/362)) Fix Dependency Injection, which prevented to save the CalendarRange   
+* ([#368](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/368)) fix search query for user groups   
+
+## v3.9.2 - 2025-02-27
+### Fixed
+* Use fetchResults method to fetch all social issues instead of only the first page   
+
+## v3.9.1 - 2025-02-27
+### Fixed
+* Fix post/patch request with missing 'type' property for gender   
+
+## v3.9.0 - 2025-02-27
+### Feature
+* ([#349](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/349)) Suggest all referrers within actions of the accompanying period when creating an activity   
+* ([#343](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/343)) Add possibility to export a csv with all social issues and social actions   
+* ([#360](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/360)) Restore document to previous kept version when a workflow is canceled   
+* ([#341](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/341)) Add a list of third parties from within the admin (csv download)   
+### Fixed
+* fix generation of document with accompanying period context, and list of activities and works   
+### DX
+* ([#333](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/333)) Create an unique source of trust for translations   
+
+## v3.8.2 - 2025-02-10
+### Fixed
+* ([#358](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/358)) Remove "filter" button on list of documents in the workflow's "add attachement" modal   
+
+## v3.8.1 - 2025-02-05
+### Fixed
+* Fix household link in the parcours banner   
+
+## v3.8.0 - 2025-02-03
+### Feature
+* Improve the UX of the news item admin form to prevent wrong usage
+* ([#319](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/319)) Notification list: display the concerned person's badges in the list
+* ([#320](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/320)) Show the first 3 persons directly in the accompanying period's banner
+* ([#334](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/334)) Suggest current user when creating an activity
+* ([#331](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/331)) Add attachments to workflows
+### Fixed
+* ([#350](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/350)) Add validation error to manual selection of person in PersonDuplicateController
+* ([#354](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/354)) Fix document category creation
+* ([#351](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/351)) Add definitive whitespace between span elements in vue PersonText component
+
+## v3.7.1 - 2025-01-21
+### Fixed
+* Fix legacy configuration processor for notifier component   
+
+## v3.7.0 - 2025-01-21
+### Feature
+* Use the Notifier component from Symfony to sens short messages (SMS). This allow to use more provider.
+### Fixed
+* ([#348](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/348)) [export] Fix aggregation of referrer's scope and job: fix the date range comparison
+
+### Warning on configuration of Notifier component
+
+If installed in an symfony app where the recipes are activated, this configuration should be added automatically:
+
+```yaml
+framework:
+    notifier:
+        chatter_transports:
+        texter_transports:
+            ovhcloud: '%env(OVHCLOUD_DSN)%'
+        channel_policy:
+            # use chat/slack, chat/telegram, sms/twilio or sms/nexmo
+            urgent: ['email']
+            high: ['email']
+            medium: ['email']
+            low: ['email']
+        admin_recipients:
+            - { email: admin@example.com }
+```
+
+Actually, you should either:
+
+- remove the configuration of ovhcloud added by the recipe
+- or remove the previous configuration of chill, to avoid keeping legacy configuration
+
+#### Remove the added configuration and keep the legacy configuration
+
+To remove the configuration:
+
+```diff
+framework:
+    notifier:
+        chatter_transports:
+        texter_transports:
+-            ovhcloud: '%env(OVHCLOUD_DSN)%'
+```
+
+In that case, the previous configuration, which was stored under the `chill_main.short_messages.dsn` will be reconfigured into the Notifier component's configuration.
+
+#### Properly configure SMS
+
+You can also properly configure it, as [described in the OVH cloud provider repository](https://github.com/symfony/ovh-cloud-notifier/tree/5.4?tab=readme-ov-file#dsn-example) (where the scheme is `ovhcloud`):
+
+**NOTE**: You have access to all notifier available with the [Notifier component](https://symfony.com/doc/current/notifier.html#notifier-sms-channel). You are not restricted to use OVH as a provider.
+
+```diff
+framework:
+    notifier:
+        chatter_transports:
+        texter_transports:
++            ovhcloud: '%env(OVHCLOUD_DSN)%' # this value should be located in a variable, and have `ovhcloud://` as a scheme
+
+chill_main:
+-    short_messages:
+-        dsn: '%env(string:SHORT_MESSAGE_DSN)%'
+```
+
+## v3.6.0 - 2025-01-16
+### Feature
+* Importer for addresses does not fails when the postal code is not found with some addresses, and compute a recap list of all addresses that could not be imported. This recap list can be send by email. 
+* ([#346](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/346)) Create a driver for storing documents on disk (instead of openstack object store)
+ 
+* Add address importer from french Base d'Adresse Nationale (BAN) 
+* ([#343](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/343)) Add csv export for social issues and social actions 
+### Fixed
+* Export: fix missing alias in activity between certain dates filter. Condition added for alias. 
+
+## v3.5.3 - 2025-01-07
+### Fixed
+* Fix the EntityToJsonTransformer to return an empty array if the value is "" 
+
+## v3.5.2 - 2024-12-19
+### Fixed
+* ([#345](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/345)) Export: activity filtering of users that were associated to an activity between certain dates. Results contained activities that were not within the specified date range" 
+
+## v3.5.1 - 2024-12-16
+### Fixed
+* Filiation: fix the display of the gender label in the graph 
+* Wrap handling of PdfSignedMessage into transactions 
+
+## v3.5.0 - 2024-12-09
+### Feature
+* ([#318](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/318)) Show all the pages of the documents in the signature app 
+### Fixed
+* Wrap the signature's change state into a transaction, to avoid race conditions 
+* Fix display of gender label 
+
+## v3.4.3 - 2024-12-05
+### Fixed
+* Remove the "not null" constraint on person supplementary phones
+* Remove doctrine annotation that prevent from adding documents to activities
+
 ## v3.4.2 - 2024-12-05
 ### Fixed
 * ([#329](https://gitlab.com/Chill-Projet/chill-bundles/-/issues/329)) Fix the serialization of gender for the generation of documents 

CONVENTIONS-en.md

@@ -0,0 +1,386 @@
+# Chill Conventions
+
+In Progress
+
+## Translations
+
+Per bundle, all translations for Twig pages are located in a single file: translations/messages.fr.yaml.
+
+## File Locations
+
+    Controllers, form types, and Twig templates are placed in the root folders Controller, Form, and Resources/views, respectively.
+    Admin pages are no longer placed in subfolders under Admin.
+
+## Assets: Entrypoint Naming
+
+There are three types of entry points:
+
+* Vue application-specific (often for a single page): Prefixed with vue_.
+  * Reusable JavaScript/CSS code:
+      Examples include:
+          * ckeditor
+          * async_upload (used for forms)
+          * bootstrap
+          * chill.js
+          * ...
+        => We prefix with `mod_`
+
+  * Page-specific CSS/JS:
+      * Often reuses functionalities like ShowHide.
+        => We prefix with `page_`.
+
+## Folder Structure
+
+````
+# Under Resources/public:
+
+    - chill/ => Contains the theme (Chill).
+        - chillmain.scss: Compiled into the chill entrypoint.
+    - lib/ => Libraries never used as entrypoints but reused elsewhere.
+        - Examples: ShowHide, Collection, Select2.
+    - module/: Ends up in reusable entrypoints (mod_).
+        - bootstrap
+            - custom.scss
+            - custom/
+                - variable.scss
+                - ...
+        - AsyncUpload.
+    - vue/ => Vue applications only (vue_).
+        - Examples: _components, app.
+    - page/ => Page-specific assets (page_).
+        - login
+        - person
+        - personvendee
+        - household_edit_metadata
+            - index.js
+````
+
+# Stylesheet Organization
+
+1. The mod_bootstrap (module bootstrap) entry point is the first level. All parts (modules) of bootstrap are included in the bootstrap.js file located in ChillMainBundle/Resources/public/module/bootstrap.
+
+    * At the beginning, this file imports the variables.scss file, which determines most of the bootstrap settings as customized. This file overrides the original, and many variables are adjusted for Chill.
+        * Care must be taken to ensure this file can always be compared to the original bootstrap file. In the event of a bootstrap update, a diff must be generated and this diff applied to the variable file of the new version.
+    * At the end, it imports the custom.scss file, which includes bootstrap adaptations to prepare it for our Chill theme.
+        * This `custom.scss` file can be split into smaller files using `@import 'custom/...'`.
+    * The idea is that this first bootstrap layer sets an important part of the application’s styles, particularly those related to layout positioning, responsive breakpoints, and the default margins and spacing applied to elements being manipulated.
+
+2. The chill entry point is the second level. It contains the Chill theme, which is recognizable in the application.
+
+    * Each bundle has a `Resources/public/chill` folder containing a main sass file, which can optionally be split using `@imports`. All these files are compiled into a single Chill entry point, which serves as the application’s theme and overrides bootstrap.
+    * The chillmain.scss file should contain the most general style cascades, those applied to many areas of the application.
+    * The chillperson.scss file also includes styles specific to different contexts related to people: person, household, and accompanying course.
+    * Some smaller bundles contain only styles specific to their functionality.
+
+3. The vue_ entry points are used for Vue components. Vue files can contain an scss style block. These styles are specific to the component and its inheritance, with the scoped tag precisely defining their scope (see the documentation).
+
+4. The page_ entry points are used to add assets specific to certain pages, most often scripts and styles.
+
+## HTML Tagging and Style Cascades
+
+The following example shows how to tag a code element without overdoing it. Note that:
+
+* It is not necessary to tag all inner classes.
+* The parent class should not be repeated in all child classes. Sass cascading allows for flexible HTML structuring without overloading the tag hierarchy.
+* Often, the first class will have variations created with additional classes that start in the same way: bloc-dark simply adds the dark version of bloc. We do not use bloc dark because we don’t want the dark class of bloc to interact with the same dark class of table. As a result, we will have an element bloc bloc-dark and another element table table-dark.
+
+```html
+<div class="bloc bloc-dark my-bloc">
+  <h3>My Title</h3>
+  <ul class="record_actions">
+    <li>
+      <a class="btn btn-edit"></a>
+    </li>
+  </ul>
+</div>
+```
+
+Finally, it is important to define what a block, an action zone, and a button are. These three elements exist independently and are the only ones we tag.
+
+For example, to style the title, we simply specify h3 within the block cascade.
+
+```scss
+div.bloc {
+    // un bloc générique, utilisé à plusieurs endroits
+    &.bloc-dark {
+        // la version sombre du bloc
+    }
+    h3 {}
+    ul {
+        // une liste standard dans bloc
+        li {
+            // des items de liste standard dans bloc
+        }
+    }
+}
+div.mon-bloc {
+    // des exceptions spécifiques à mon-bloc,
+    // qui sont des adaptations de bloc
+}
+
+ul.record_actions {
+    // va uniformiser tous les record_actions de l'application
+    li {
+        //...
+    }
+}
+
+.btn {
+    // les boutons de bootstrap
+    .btn-edit {
+        // chill étends les boutons bootstrap pour ses propres besoins
+    }
+}
+</style>
+```
+## Render box
+
+## URL
+
+## Route Naming Conventions
+
+:::warning
+These rules have not always been followed in the past. They are desired for the future.
+:::
+
+Routes follow this structure:
+
+`chill_(api|crud)_bundle_(api)_entity_action`
+
+1. First, chill_ (for all Chill modules).
+2. Then, crud or api, optional, automatically added if the route is generated by the configuration.
+3. Then, a string indicating the bundle (`main`, `person`, `activity`, ...).
+4. Then, api, if the route is an API route.
+5. Then, a string indicating the entity the route targets, and possibly the sub-entities.
+6. Then, an action (`list`, `view`, `edit`, `new`, ...).
+
+Indicating `api` in the fourth position allows distinguishing API routes generated by the configuration (which are all prefixed with `chill_api`) from those generated manually. (For example: `chill_api_household__index` and `chill_person_api_household_members_move`).
+
+If points 4 and 5 are missing, they are replaced by other elements to ensure the uniqueness of the route and its clear understanding.
+
+#### HTML pages
+
+:::warning
+These rules have not always been followed in the past. They are desired for the future.
+:::
+
+Syntaxe:
+
+```
+/{_locale}/bundle/entity/{id}/action
+/{_locale}/bundle/entity/sub-entity/{id}/action
+```
+
+The following elements should be included in the list:
+
+1. The locale;
+2. An identifier for the bundle;
+3. The entity it relates to;
+4. Any sub-entities that the URL refers to;
+5. The action.
+
+```
+# list of activities for a person
+/fr/activity/person/25/activity/list
+
+# new activity
+/fr/activity/activity/new?person_id=25
+
+```
+
+#### Pour les API
+
+:::info
+Automatically generated routes are prefixed with `chill_api`
+:::
+
+Syntaxe:
+
+```
+/api/1.0/bundle/entity/{id}/action
+/api/1.0/bundle/entity/sub-entity/{id}/action
+```
+
+The following elements should be included in the list:
+
+1. The string `/api/` followed by the version (e.g., 1.0);
+2. An identifier for the bundle;
+3. The entity it relates to;
+4. Any sub-entities that the URL refers to;
+5. The action.
+
+These elements may be interspersed with the entity identifier. In this case, the identifier should be placed immediately after the entity it relates to.
+
+#### URLS for admin pages
+Same conventions as for other html pages, **but `admin` is added in second position**. Soit:
+
+`/{_locale}/admin/bundle/entity/{id}/action`
+
+## Database table naming convention
+
+When creating a new entity and the corresponding database table, we follow the following naming convention for the database table:
+
+`chill_{bundle_identifier}_{entity_name}`.
+Eg. chill_person_spoken_languages
+
+## UI Rules
+
+### Page Titles
+#### Every page must have a title (in the head tag and page header).
+
+Each page contains a title in the <head> tag. This title is typically the same as the header title on the page.
+
+Tip: It is possible to use the block function in Twig for this.
+
+Example:
+
+```htmlmixed=
+{% block title "Titre de la page" %}
+
+{% block content %}
+<h1>
+    {{ block('title')}}
+</h1>
+{% endblock %}
+```
+
+### entity_render usage
+
+#### in Twig
+Always use chill_entity_render_box for rendering entities like:
+* User
+* Person
+* SocialAction
+* SocialIssue
+* Address
+* Thirdparty
+* ...
+
+Example:
+
+```
+address|chill_entity_render_box
+```
+Justification:
+
+1. Customization by installation: Some elements are sometimes customized during installation (for example, the name of each user will be followed by the name of the service).
+2. To streamline and make displays consistent: Ensures uniformity in the way information is displayed across different pages or sections.
+3. To simplify Twig code: By using blocks and centralizing title logic, it reduces repetition and makes the Twig code easier to maintain.
+
+* Three rendering modes:
+  * inline
+  * block
+  * item.
+
+#### In Vue
+
+There is always a renderbox equivalent in vue.
+
+#### HTML Links to Sections
+
+Always include links/icons for accessing records, such as person or household details, if the user has access.
+
+### Form Guidelines
+
+#### Vocabulary:
+* `Create` in a `bt bt-create` for links to the form to create an entity (to access the form).
+* `Save` in a `bt bt-save` for "Save" buttons (in either an edit or create form).
+* `Save and new`
+* `Save and view`
+* `Edit` in a `bt bt-edit` for links to the edit form.
+* `Duplicate` (specify where it can be seen).
+* `Cancel` for leaving an edit page with a link to the list, or the `returnPath`.
+
+#### After Saving:
+
+Redirect to the returnPath if available; otherwise, redirect to the view page.
+
+### Sticky Form Buttons:
+
+Buttons like "Cancel" and "Save" must be within a "sticky-form" bar at the bottom of the form.
+
+If relevant:
+
+* The banner contains a "Cancel" button that returns to the previous page. It is mandatory for forms, but optional for lists or "summary" pages.
+* This "Cancel" button is always on the left.
+
+```
+<ul class="record_actions sticky-form-buttons">
+    <li class="cancel">
+        <a href="{{ chill_entity_return_path('route_name' { 'route': 'option' } )}}">{{ return_path_label }}</a>
+    </li>
+    <li>
+        <!-- action 1 -->
+    </li>
+</ul>
+```
+
+### Flash Messages
+
+#### Display a flash message upon entity creation:
+
+Everytime an entity has been created
+
+> "The entity has been created."
+
+The name of the element can be replaced with something more relevant:
+
+> * The activity has been created
+> * The appointment has been created
+> * ...
+
+#### On Saving an Entity
+
+Each time an entity is saved, a flash message should appear:
+
+> The data has been modified
+
+#### Form Error (Validation Error)
+
+At the top of the form, a flash message should indicate that validations have failed:
+
+> This form contains errors
+
+Errors should appear attached to the field they concern. However, it is acceptable to display errors at the root of the form if it is technically difficult to attach errors.
+
+### Return Links
+
+Each time a link is provided, check whether the function chill_return_path, chill_forward_return_path, or chill_return_path_or should be used.
+* From the list page, to the opening of an element, or the creation button => use chill_path_add_return_path
+* In these edit pages:
+        * use chill_return_path_or in the "Cancel" button;
+        * for the "Save and view" and "Save and close" buttons => ?
+
+### Assets for Suggestion Lists
+
+Create a list of suggestions to add (the entire item is clickable)
+
+```html
+<ul class="list-suggest add-items">
+   <li>
+      <span>item</span>
+   </li>
+</ul>
+```
+
+Create a list of suggestions to remove (with a clickable red cross, the anchor <a> is empty)
+
+```html
+<ul class="list-suggest remove-items">
+    <li>
+        <span>
+            item
+        </span>
+    </li>
+</ul>
+```
+
+Create a removable title (with a clickable red cross, the anchor <a> is empty)
+
+```html
+<div class="item-title">
+    <span>title</span>
+</div>
+```
+
+The classes `cols` or `inline` can be added alongside `list-suggest` to modify the layout of the list. In the last example, add a `removable` class to the `<span>` if you want to make the item removable.

CONVENTIONS-fr.md

@@ -4,7 +4,6 @@ en cours de rédaction
 
 ## Translations
 
-
 Par bundle, toutes les traductions des pages twig se trouvent dans un seul fichier `translations/messages.fr.yaml`.
 
 ## Emplacement des fichiers
@@ -142,7 +141,6 @@ ul.record_actions {
 
 ## Render box
 
-
 ## URL
 
 ### Nommage des routes
@@ -234,6 +232,13 @@ Même conventions que dans les autres pages html de l'application, **mais `admin
 
 `/{_locale}/admin/bundle/entity/{id}/action`
 
+### Nommage des tables de base de donnée
+
+Lors de la création d'une nouvelle entité et de la table de base de données correspondante, nous suivons la convention d'appellation suivante pour la table de base de données :
+
+`chill_{bundle_identifier}_{nom_de_l'entité}`.
+
+Par exemple : chill_person_spoken_languages
 
 ## Règles UI chill
 
@@ -293,8 +298,6 @@ A prevoir:
 
 > quand on passe l’option render: bloc, on peut placer le render_box dans une boucle for plus large qui fonctionne avec la classe flex-table ou la classe flex-bloc, ce qui donnera un affichage en rangée (table) ou en blocs. [name=Mathieu]
 
-
-
 #### En vue
 
 Il existe systématiquement une "box" équivalente en vue.

assets/translator.ts

@@ -0,0 +1,7 @@
+import { trans, setLocale, setLocaleFallbacks } from "./ux-translator";
+
+setLocaleFallbacks({"en": "fr", "nl": "fr", "fr": "en"});
+setLocale('fr');
+
+export { trans };
+export * from '../var/translations';

assets/ux-translator/README.md

@@ -0,0 +1,3 @@
+This directory import the symfony ux-translator files directly into chill-bundles.
+
+This remove the yarn dependencies from the real package, which breaks our installation.

assets/ux-translator/dist/formatters/formatter.d.ts

@@ -0,0 +1 @@
+export declare function format(id: string, parameters: Record<string, string | number>, locale: string): string;

assets/ux-translator/dist/formatters/intl-formatter.d.ts

@@ -0,0 +1 @@
+export declare function formatIntl(id: string, parameters: Record<string, string | number>, locale: string): string;

assets/ux-translator/dist/translator.d.ts

@@ -0,0 +1,27 @@
+export type DomainType = string;
+export type LocaleType = string;
+export type TranslationsType = Record<DomainType, {
+    parameters: ParametersType;
+}>;
+export type NoParametersType = Record<string, never>;
+export type ParametersType = Record<string, string | number | Date> | NoParametersType;
+export type RemoveIntlIcuSuffix<T> = T extends `${infer U}+intl-icu` ? U : T;
+export type DomainsOf<M> = M extends Message<infer Translations, LocaleType> ? keyof Translations : never;
+export type LocaleOf<M> = M extends Message<TranslationsType, infer Locale> ? Locale : never;
+export type ParametersOf<M, D extends DomainType> = M extends Message<infer Translations, LocaleType> ? Translations[D] extends {
+    parameters: infer Parameters;
+} ? Parameters : never : never;
+export interface Message<Translations extends TranslationsType, Locale extends LocaleType> {
+    id: string;
+    translations: {
+        [domain in DomainType]: {
+            [locale in Locale]: string;
+        };
+    };
+}
+export declare function setLocale(locale: LocaleType | null): void;
+export declare function getLocale(): LocaleType;
+export declare function throwWhenNotFound(enabled: boolean): void;
+export declare function setLocaleFallbacks(localeFallbacks: Record<LocaleType, LocaleType>): void;
+export declare function getLocaleFallbacks(): Record<LocaleType, LocaleType>;
+export declare function trans<M extends Message<TranslationsType, LocaleType>, D extends DomainsOf<M>, P extends ParametersOf<M, D>>(...args: P extends NoParametersType ? [message: M, parameters?: P, domain?: RemoveIntlIcuSuffix<D>, locale?: LocaleOf<M>] : [message: M, parameters: P, domain?: RemoveIntlIcuSuffix<D>, locale?: LocaleOf<M>]): string;

assets/ux-translator/dist/translator_controller.d.ts

@@ -0,0 +1 @@
+export * from './translator';

assets/ux-translator/dist/translator_controller.js

@@ -0,0 +1,283 @@
+import { IntlMessageFormat } from 'intl-messageformat';
+
+function strtr(string, replacePairs) {
+    const regex = Object.entries(replacePairs).map(([from]) => {
+        return from.replace(/([-[\]{}()*+?.\\^$|#,])/g, '\\$1');
+    });
+    if (regex.length === 0) {
+        return string;
+    }
+    return string.replace(new RegExp(regex.join('|'), 'g'), (matched) => replacePairs[matched].toString());
+}
+
+function format(id, parameters, locale) {
+    if (null === id || '' === id) {
+        return '';
+    }
+    if (typeof parameters['%count%'] === 'undefined' || Number.isNaN(parameters['%count%'])) {
+        return strtr(id, parameters);
+    }
+    const number = Number(parameters['%count%']);
+    let parts = [];
+    if (/^\|+$/.test(id)) {
+        parts = id.split('|');
+    }
+    else {
+        parts = id.match(/(?:\|\||[^|])+/g) || [];
+    }
+    const intervalRegex = /^(?<interval>({\s*(-?\d+(\.\d+)?[\s*,\s*\-?\d+(.\d+)?]*)\s*})|(?<left_delimiter>[[\]])\s*(?<left>-Inf|-?\d+(\.\d+)?)\s*,\s*(?<right>\+?Inf|-?\d+(\.\d+)?)\s*(?<right_delimiter>[[\]]))\s*(?<message>.*?)$/s;
+    const standardRules = [];
+    for (let part of parts) {
+        part = part.trim().replace(/\|\|/g, '|');
+        const matches = part.match(intervalRegex);
+        if (matches) {
+            const matchGroups = matches.groups || {};
+            if (matches[2]) {
+                for (const n of matches[3].split(',')) {
+                    if (number === Number(n)) {
+                        return strtr(matchGroups.message, parameters);
+                    }
+                }
+            }
+            else {
+                const leftNumber = '-Inf' === matchGroups.left ? Number.NEGATIVE_INFINITY : Number(matchGroups.left);
+                const rightNumber = ['Inf', '+Inf'].includes(matchGroups.right)
+                    ? Number.POSITIVE_INFINITY
+                    : Number(matchGroups.right);
+                if (('[' === matchGroups.left_delimiter ? number >= leftNumber : number > leftNumber) &&
+                    (']' === matchGroups.right_delimiter ? number <= rightNumber : number < rightNumber)) {
+                    return strtr(matchGroups.message, parameters);
+                }
+            }
+        }
+        else {
+            const ruleMatch = part.match(/^\w+:\s*(.*?)$/);
+            standardRules.push(ruleMatch ? ruleMatch[1] : part);
+        }
+    }
+    const position = getPluralizationRule(number, locale);
+    if (typeof standardRules[position] === 'undefined') {
+        if (1 === parts.length && typeof standardRules[0] !== 'undefined') {
+            return strtr(standardRules[0], parameters);
+        }
+        throw new Error(`Unable to choose a translation for "${id}" with locale "${locale}" for value "${number}". Double check that this translation has the correct plural options (e.g. "There is one apple|There are %count% apples").`);
+    }
+    return strtr(standardRules[position], parameters);
+}
+function getPluralizationRule(number, locale) {
+    number = Math.abs(number);
+    let _locale = locale;
+    if (locale === 'pt_BR' || locale === 'en_US_POSIX') {
+        return 0;
+    }
+    _locale = _locale.length > 3 ? _locale.substring(0, _locale.indexOf('_')) : _locale;
+    switch (_locale) {
+        case 'af':
+        case 'bn':
+        case 'bg':
+        case 'ca':
+        case 'da':
+        case 'de':
+        case 'el':
+        case 'en':
+        case 'en_US_POSIX':
+        case 'eo':
+        case 'es':
+        case 'et':
+        case 'eu':
+        case 'fa':
+        case 'fi':
+        case 'fo':
+        case 'fur':
+        case 'fy':
+        case 'gl':
+        case 'gu':
+        case 'ha':
+        case 'he':
+        case 'hu':
+        case 'is':
+        case 'it':
+        case 'ku':
+        case 'lb':
+        case 'ml':
+        case 'mn':
+        case 'mr':
+        case 'nah':
+        case 'nb':
+        case 'ne':
+        case 'nl':
+        case 'nn':
+        case 'no':
+        case 'oc':
+        case 'om':
+        case 'or':
+        case 'pa':
+        case 'pap':
+        case 'ps':
+        case 'pt':
+        case 'so':
+        case 'sq':
+        case 'sv':
+        case 'sw':
+        case 'ta':
+        case 'te':
+        case 'tk':
+        case 'ur':
+        case 'zu':
+            return 1 === number ? 0 : 1;
+        case 'am':
+        case 'bh':
+        case 'fil':
+        case 'fr':
+        case 'gun':
+        case 'hi':
+        case 'hy':
+        case 'ln':
+        case 'mg':
+        case 'nso':
+        case 'pt_BR':
+        case 'ti':
+        case 'wa':
+            return number < 2 ? 0 : 1;
+        case 'be':
+        case 'bs':
+        case 'hr':
+        case 'ru':
+        case 'sh':
+        case 'sr':
+        case 'uk':
+            return 1 === number % 10 && 11 !== number % 100
+                ? 0
+                : number % 10 >= 2 && number % 10 <= 4 && (number % 100 < 10 || number % 100 >= 20)
+                    ? 1
+                    : 2;
+        case 'cs':
+        case 'sk':
+            return 1 === number ? 0 : number >= 2 && number <= 4 ? 1 : 2;
+        case 'ga':
+            return 1 === number ? 0 : 2 === number ? 1 : 2;
+        case 'lt':
+            return 1 === number % 10 && 11 !== number % 100
+                ? 0
+                : number % 10 >= 2 && (number % 100 < 10 || number % 100 >= 20)
+                    ? 1
+                    : 2;
+        case 'sl':
+            return 1 === number % 100 ? 0 : 2 === number % 100 ? 1 : 3 === number % 100 || 4 === number % 100 ? 2 : 3;
+        case 'mk':
+            return 1 === number % 10 ? 0 : 1;
+        case 'mt':
+            return 1 === number
+                ? 0
+                : 0 === number || (number % 100 > 1 && number % 100 < 11)
+                    ? 1
+                    : number % 100 > 10 && number % 100 < 20
+                        ? 2
+                        : 3;
+        case 'lv':
+            return 0 === number ? 0 : 1 === number % 10 && 11 !== number % 100 ? 1 : 2;
+        case 'pl':
+            return 1 === number
+                ? 0
+                : number % 10 >= 2 && number % 10 <= 4 && (number % 100 < 12 || number % 100 > 14)
+                    ? 1
+                    : 2;
+        case 'cy':
+            return 1 === number ? 0 : 2 === number ? 1 : 8 === number || 11 === number ? 2 : 3;
+        case 'ro':
+            return 1 === number ? 0 : 0 === number || (number % 100 > 0 && number % 100 < 20) ? 1 : 2;
+        case 'ar':
+            return 0 === number
+                ? 0
+                : 1 === number
+                    ? 1
+                    : 2 === number
+                        ? 2
+                        : number % 100 >= 3 && number % 100 <= 10
+                            ? 3
+                            : number % 100 >= 11 && number % 100 <= 99
+                                ? 4
+                                : 5;
+        default:
+            return 0;
+    }
+}
+
+function formatIntl(id, parameters, locale) {
+    if (id === '') {
+        return '';
+    }
+    const intlMessage = new IntlMessageFormat(id, [locale.replace('_', '-')], undefined, { ignoreTag: true });
+    parameters = { ...parameters };
+    Object.entries(parameters).forEach(([key, value]) => {
+        if (key.includes('%') || key.includes('{')) {
+            delete parameters[key];
+            parameters[key.replace(/[%{} ]/g, '').trim()] = value;
+        }
+    });
+    return intlMessage.format(parameters);
+}
+
+let _locale = null;
+let _localeFallbacks = {};
+let _throwWhenNotFound = false;
+function setLocale(locale) {
+    _locale = locale;
+}
+function getLocale() {
+    return (_locale ||
+        document.documentElement.getAttribute('data-symfony-ux-translator-locale') ||
+        (document.documentElement.lang ? document.documentElement.lang.replace('-', '_') : null) ||
+        'en');
+}
+function throwWhenNotFound(enabled) {
+    _throwWhenNotFound = enabled;
+}
+function setLocaleFallbacks(localeFallbacks) {
+    _localeFallbacks = localeFallbacks;
+}
+function getLocaleFallbacks() {
+    return _localeFallbacks;
+}
+function trans(message, parameters = {}, domain = 'messages', locale = null) {
+    if (typeof domain === 'undefined') {
+        domain = 'messages';
+    }
+    if (typeof locale === 'undefined' || null === locale) {
+        locale = getLocale();
+    }
+    if (typeof message.translations === 'undefined') {
+        return message.id;
+    }
+    const localesFallbacks = getLocaleFallbacks();
+    const translationsIntl = message.translations[`${domain}+intl-icu`];
+    if (typeof translationsIntl !== 'undefined') {
+        while (typeof translationsIntl[locale] === 'undefined') {
+            locale = localesFallbacks[locale];
+            if (!locale) {
+                break;
+            }
+        }
+        if (locale) {
+            return formatIntl(translationsIntl[locale], parameters, locale);
+        }
+    }
+    const translations = message.translations[domain];
+    if (typeof translations !== 'undefined') {
+        while (typeof translations[locale] === 'undefined') {
+            locale = localesFallbacks[locale];
+            if (!locale) {
+                break;
+            }
+        }
+        if (locale) {
+            return format(translations[locale], parameters, locale);
+        }
+    }
+    if (_throwWhenNotFound) {
+        throw new Error(`No translation message found with id "${message.id}".`);
+    }
+    return message.id;
+}
+
+export { getLocale, getLocaleFallbacks, setLocale, setLocaleFallbacks, throwWhenNotFound, trans };

assets/ux-translator/dist/utils.d.ts

@@ -0,0 +1 @@
+export declare function strtr(string: string, replacePairs: Record<string, string | number>): string;

assets/ux-translator/package.json

@@ -0,0 +1,34 @@
+{
+    "name": "@symfony/ux-translator",
+    "description": "Symfony Translator for JavaScript",
+    "license": "MIT",
+    "version": "1.0.0",
+    "main": "dist/translator_controller.js",
+    "types": "dist/translator_controller.d.ts",
+    "scripts": {
+        "build": "node ../../../bin/build_package.js .",
+        "watch": "node ../../../bin/build_package.js . --watch",
+        "test": "../../../bin/test_package.sh .",
+        "check": "biome check",
+        "ci": "biome ci"
+    },
+    "symfony": {
+        "importmap": {
+            "intl-messageformat": "^10.5.11",
+            "@symfony/ux-translator": "path:%PACKAGE%/dist/translator_controller.js",
+            "@app/translations": "path:var/translations/index.js",
+            "@app/translations/configuration": "path:var/translations/configuration.js"
+        }
+    },
+    "peerDependencies": {
+        "intl-messageformat": "^10.5.11"
+    },
+    "peerDependenciesMeta": {
+        "intl-messageformat": {
+            "optional": false
+        }
+    },
+    "devDependencies": {
+        "intl-messageformat": "^10.5.11"
+    }
+}

composer.json

@@ -13,8 +13,10 @@
         "ext-json": "*",
         "ext-openssl": "*",
         "ext-redis": "*",
-        "champs-libres/wopi-bundle": "dev-master@dev",
+        "ext-zlib": "*",
+        "champs-libres/wopi-bundle": "dev-symfony-v5@dev",
         "champs-libres/wopi-lib": "dev-master@dev",
+        "doctrine/data-fixtures": "^1.8",
         "doctrine/doctrine-bundle": "^2.1",
         "doctrine/doctrine-migrations-bundle": "^3.0",
         "doctrine/orm": "^2.13.0",
@@ -56,7 +58,9 @@
         "symfony/messenger": "^5.4",
         "symfony/mime": "^5.4",
         "symfony/monolog-bundle": "^3.5",
+        "symfony/notifier": "^5.4",
         "symfony/options-resolver": "^5.4",
+        "symfony/ovh-cloud-notifier": "^5.4",
         "symfony/process": "^5.4",
         "symfony/property-access": "^5.4",
         "symfony/property-info": "^5.4",
@@ -71,6 +75,7 @@
         "symfony/templating": "^5.4",
         "symfony/translation": "^5.4",
         "symfony/twig-bundle": "^5.4",
+        "symfony/ux-translator": "^2.22",
         "symfony/validator": "^5.4",
         "symfony/webpack-encore-bundle": "^1.11",
         "symfony/workflow": "^5.4",
@@ -85,6 +90,7 @@
     "require-dev": {
         "doctrine/doctrine-fixtures-bundle": "^3.3",
         "fakerphp/faker": "^1.13",
+        "friendsofphp/php-cs-fixer": "3.65.0",
         "jangregor/phpstan-prophecy": "^1.0",
         "nelmio/alice": "^3.8",
         "nikic/php-parser": "^4.15",
@@ -95,6 +101,7 @@
         "phpstan/phpstan-strict-rules": "^1.0",
         "phpunit/phpunit": "^10.5.24",
         "rector/rector": "^1.1.0",
+        "symfony/amqp-messenger": "^5.4.45",
         "symfony/debug-bundle": "^5.4",
         "symfony/dotenv": "^5.4",
         "symfony/flex": "^2.4",
@@ -156,7 +163,9 @@
             "cache:clear": "symfony-cmd",
             "assets:install %PUBLIC_DIR%": "symfony-cmd"
         },
-        "php-cs-fixer": "php-cs-fixer fix --config=./.php-cs-fixer.dist.php --show-progress=none"
+        "php-cs-fixer": "php-cs-fixer fix --config=./.php-cs-fixer.dist.php --show-progress=none",
+        "phpstan":  "phpstan --no-progress",
+        "rector": "rector --no-progress-bar"
     },
     "extra": {
         "symfony": {

config/bundles.php

@@ -2,7 +2,6 @@
 
 return [
     Symfony\Bundle\FrameworkBundle\FrameworkBundle::class => ['all' => true],
-    loophp\PsrHttpMessageBridgeBundle\PsrHttpMessageBridgeBundle::class => ['all' => true],
     ChampsLibres\WopiBundle\WopiBundle::class => ['all' => true],
     Doctrine\Bundle\DoctrineBundle\DoctrineBundle::class => ['all' => true],
     Doctrine\Bundle\FixturesBundle\DoctrineFixturesBundle::class => ['dev' => true, 'test' => true],
@@ -36,4 +35,6 @@ return [
     Chill\BudgetBundle\ChillBudgetBundle::class => ['all' => true],
     Chill\WopiBundle\ChillWopiBundle::class => ['all' => true],
     Symfony\Bundle\WebProfilerBundle\WebProfilerBundle::class => ['dev' => true, 'test' => true],
+    Symfony\UX\Translator\UxTranslatorBundle::class => ['all' => true],
+    loophp\PsrHttpMessageBridgeBundle\PsrHttpMessageBridgeBundle::class => ['all' => true],
 ];

config/packages/chill.yaml

@@ -1,6 +1,13 @@
 chill_main:
-    available_languages: [ '%env(resolve:LOCALE)%', 'en' ]
+    available_languages: [ '%env(resolve:LOCALE)%', 'en', 'nl' ]
     available_countries: ['BE', 'FR']
+    top_banner:
+        visible: false
+        text:
+            fr: 'Vous travaillez actuellement avec la version de PRÉ-PRODUCTION.'
+            nl: 'Je werkt momenteel in de PRE-PRODUCTIE versie'
+        color: '#353535'
+        background_color: '#d8bb48'
     notifications:
         from_email: '%env(resolve:NOTIFICATION_FROM_EMAIL)%'
         from_name: '%env(resolve:NOTIFICATION_FROM_NAME)%'
@@ -17,6 +24,7 @@ chill_main:
     acl:
         form_show_scopes: true
         form_show_centers: true
+        filter_stats_by_center: true
     access_global_history: false
     access_user_change_password: true
     access_permissions_group_list: true

config/packages/chill_aside_activity.yaml

@@ -0,0 +1,2 @@
+chill_aside_activity:
+    show_concerned_persons_count: hidden

config/packages/chill_doc_store.yaml

@@ -1,4 +1,7 @@
 chill_doc_store:
+    use_driver: openstack
+    local_storage:
+        storage_path: '%kernel.project_dir%/var/storage'
     openstack:
         temp_url:
             temp_url_key:         '%env(resolve:ASYNC_UPLOAD_TEMP_URL_KEY)%'       # Required

config/packages/chill_workflow_signature_documents.yaml

@@ -0,0 +1,11 @@
+chill_main:
+    workflow_signature:
+        base_signer:
+            document_kinds:
+                - { key: id_card, labels: [ { lang: fr, label: "Carte d'identité" } ] }
+                - { key: passport, labels: [ { lang: fr, label: "Passeport" } ] }
+                - { key: drivers_license, labels: [ { lang: fr, label: "Permis de conduire" } ] }
+                - { key: visa_long_stay, labels: [ { lang: fr, label: "Visa de long séjour" } ] }
+                - { key: resident_permit, labels: [ { lang: fr, label: "Carte de séjour" } ] }
+                - { key: residency_card, labels: [ { lang: fr, label: "Carte de résident" } ] }
+                - { key: provisionary_residency_permit, labels: [ { lang: fr, label: "Autorisation provisoire de séjour" } ] }

config/packages/messenger.yaml

@@ -5,7 +5,6 @@ framework:
 
         # Uncomment this (and the failed transport below) to send failed messages to this transport for later handling.
         failure_transport: failed
-
         transports:
             # those transports are added by chill-bundles recipes
             sync: sync://
@@ -19,7 +18,9 @@ framework:
                         async: ~
                     auto_setup: true
 
-            priority: '%env(MESSENGER_TRANSPORT_DSN)%/priority'
+            priority:
+                dsn: '%env(MESSENGER_TRANSPORT_DSN)%/priority'
+
             # end of transports added by chill-bundles recipes
             # https://symfony.com/doc/current/messenger.html#transport-configuration
             failed: 'doctrine://default?queue_name=failed'
@@ -61,6 +62,10 @@ framework:
             'Chill\MainBundle\Workflow\Messenger\PostSignatureStateChangeMessage': priority
             'Chill\MainBundle\Workflow\Messenger\PostPublicViewMessage': async
             'Chill\MainBundle\Service\Workflow\CancelStaleWorkflowMessage': async
+            'Chill\MainBundle\Notification\Email\NotificationEmailMessages\SendImmediateNotificationEmailMessage': async
+            'Chill\MainBundle\Export\Messenger\ExportRequestGenerationMessage': priority
+            'Chill\MainBundle\Export\Messenger\RemoveExportGenerationMessage': async
+            'Chill\MainBundle\Notification\Email\NotificationEmailMessages\ScheduleDailyNotificationDigestMessage': async
             # end of routes added by chill-bundles recipes
             # Route your messages to the transports
             # 'App\Message\YourMessage': async

config/packages/notifier.yaml

@@ -0,0 +1,13 @@
+framework:
+    notifier:
+        texter_transports:
+            #ovhcloud: '%env(OVHCLOUD_DSN)%'
+            #ovhcloud: '%env(SHORT_MESSAGE_DSN)%'
+        channel_policy:
+            # use chat/slack, chat/telegram, sms/twilio or sms/nexmo
+            urgent: ['email']
+            high: ['email']
+            medium: ['email']
+            low: ['email']
+        admin_recipients:
+            - { email: admin@example.com }

config/packages/ux_translator.yaml

@@ -0,0 +1,3 @@
+ux_translator:
+    # The directory where the JavaScript translations are dumped
+    dump_directory: '%kernel.project_dir%/var/translations'

config/packages/workflow_chill.yaml

@@ -220,6 +220,7 @@ framework:
                         - attenteModification
                         - attenteMiseEnForme
                         - attenteValidationMiseEnForme
+                        - attenteSignature
                         - attenteVisa
                         - postSignature
                         - attenteTraitement

config/routes/chill_assets_dev.yaml

@@ -0,0 +1,19 @@
+when@dev:
+    sass_assets:
+        path: /_dev/assets
+        controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
+        defaults:
+            template: '@ChillMain/Dev/dev.assets.html.twig'
+
+    sass_assets_test1:
+        path: /_dev/assets_test1
+        controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
+        defaults:
+            template: '@ChillMain/Dev/dev.assets.test1.html.twig'
+
+    sass_assets_test2:
+        path: /_dev/assets_test2
+        controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
+        defaults:
+            template: '@ChillMain/Dev/dev.assets.test2.html.twig'
+

config/routes/chill_swagger.yaml

@@ -0,0 +1,12 @@
+when@dev:
+    swagger_ui:
+        path: /_dev/swagger
+        controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
+        defaults:
+            template: '@ChillMain/Dev/swagger-ui/index.html.twig'
+
+    swagger_specs:
+        path: /_dev/specs.yaml
+        controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
+        defaults:
+            template: api/specs.yaml

docs/Makefile

@@ -1,25 +1,16 @@
-# Makefile for Sphinx documentation
+# Makefile for MkDocs documentation
 #
 
 # You can set these variables from the command line.
-SPHINXOPTS    =
-SPHINXBUILD   = sphinx-build
-PAPER         =
-BUILDDIR      = build
+MKDOCS       = mkdocs
+BUILDDIR     = site
 
-# User-friendly check for sphinx-build
-ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
-$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
+# User-friendly check for mkdocs
+ifeq ($(shell which $(MKDOCS) >/dev/null 2>&1; echo $$?), 1)
+$(error The '$(MKDOCS)' command was not found. Make sure you have MkDocs installed with 'pip install mkdocs mkdocs-material', then make sure the mkdocs executable is in your PATH.)
 endif
 
-# Internal variables.
-PAPEROPT_a4     = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
-# the i18n builder cannot share the environment and doctrees with the others
-I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest gettext
+.PHONY: help clean html serve build
 
 help:
 	@echo "Please use \`make <target>' where <target> is one of"

docs/README.md

@@ -10,20 +10,26 @@ Compilation into HTML
 
 To compile this documentation :
 
-1. Install [sphinx-doc](http://sphinx-doc.org)
+1. Install [MkDocs](https://www.mkdocs.org/) and MkDocs Material
     ``` bash
             $ virtualenv .venv # creation of the virtual env (only the first time)
             $ source .venv/bin/activate # activate the virtual env
     (.venv) $ pip install -r requirements.txt
     ```
 2. Install submodules : $ git submodule update --init;
-3. run `make html` from the root directory
-4. The base file is located on build/html/index.html
+3. run `make html` or `mkdocs build` from the root directory
+4. The base file is located on site/index.html
     ``` bash
-    $ cd build/html
+    $ cd site
     $ python -m http.server 8888 # will serve the site on the port 8888
     ```
 
+Alternatively, you can use the built-in development server:
+``` bash
+(.venv) $ mkdocs serve
+```
+This will start a development server at http://127.0.0.1:8000/ with live reload.
+
 Contribute
 ===========
 

docs/mkdocs.yml

@@ -0,0 +1,137 @@
+site_name: Chill Documentation
+site_description: Documentation for Chill - A free software for social workers
+site_url: https://docs.chill.social
+repo_url: https://gitlab.com/Chill-project/chill-bundles
+repo_name: Chill-project/chill-bundles
+
+docs_dir: source
+
+copyright: Copyright © 2014-2024 Champs-Libres Cooperative SCRLFS - GNU Free Documentation License v1.3
+
+theme:
+  name: material
+  language: en
+  features:
+    - navigation.tabs
+    - navigation.tabs.sticky
+    - navigation.sections
+    - navigation.expand
+    - navigation.path
+    - navigation.top
+    - search.highlight
+    - search.share
+    - search.suggest
+    - toc.follow
+    - content.code.copy
+    - content.code.annotate
+
+  palette:
+    # Palette toggle for light mode
+    - scheme: default
+      primary: blue
+      accent: blue
+      toggle:
+        icon: material/brightness-7
+        name: Switch to dark mode
+
+    # Palette toggle for dark mode
+    - scheme: slate
+      primary: blue
+      accent: blue
+      toggle:
+        icon: material/brightness-4
+        name: Switch to light mode
+
+  font:
+    text: Roboto
+    code: Roboto Mono
+
+plugins:
+  - search
+  - autorefs
+
+markdown_extensions:
+  - admonition
+  - pymdownx.details
+  - pymdownx.superfences
+  - pymdownx.highlight:
+      anchor_linenums: true
+      line_spans: __span
+      pygments_lang_class: true
+  - pymdownx.inlinehilite
+  - pymdownx.snippets
+  - pymdownx.tabbed:
+      alternate_style: true
+  - pymdownx.tasklist:
+      custom_checkbox: true
+  - toc:
+      permalink: true
+  - tables
+  - attr_list
+  - md_in_html
+
+nav:
+  - Home: index.md
+  - Installation:
+    - installation/index.md
+    - Development: installation/installation-development.md
+    - Production: installation/installation-production.md
+    - Document Storage: installation/document-storage.md
+    - Load Addresses: installation/load-addresses.md
+    - Production Setup: installation/prod.md
+    - Calendar SMS: installation/prod-calendar-sms-sending.md
+    - MS Graph Configuration: installation/msgraph-configure.md
+    - Enable Collabora: installation/enable-collabora-for-dev.md
+  - Development:
+    - development/index.md
+    - Access Control: development/access_control_model.md
+    - API: development/api.md
+    - Assets: development/assets.md
+    - Code Quality: development/code-quality.md
+    - Create Bundle: development/create-a-new-bundle.md
+    - Cronjobs: development/cronjob.md
+    - CRUD: development/crud.md
+    - Database Principles: development/database-principles.md
+    - Embeddable Comments: development/embeddable-comments.md
+    - Entity Info: development/entity-info.md
+    - ESLint: development/es-lint.md
+    - Exports: development/exports.md
+    - FAQ: development/FAQ.md
+    - Forms: development/forms.md
+    - Localisation: development/localisation.md
+    - Logging: development/logging.md
+    - Manual:
+      - development/manual/index.md
+      - Routing and Menus: development/manual/routing-and-menus.md
+    - Menus: development/menus.md
+    - Messages to Users: development/messages-to-users.md
+    - Migrations: development/migrations.md
+    - Pagination: development/pagination.md
+    - Render Entity: development/render-entity.md
+    - Routing: development/routing.md
+    - Run Tests: development/run-tests.md
+    - Searching: development/searching.md
+    - Timelines: development/timelines.md
+    - Useful Snippets: development/useful-snippets.md
+    - User Interface:
+      - CSS Classes: development/user-interface/css-classes.md
+      - JS Functions: development/user-interface/js-functions.md
+      - Layout Template: development/user-interface/layout-template-usage.md
+      - Widgets: development/user-interface/widgets.md
+  - Bundles:
+    - bundles/index.md
+    - Activity: bundles/activity.md
+    - Custom Fields: bundles/custom-fields.md
+    - Event: bundles/event.md
+    - Group: bundles/group.md
+    - LDAP: bundles/ldap.md
+    - Main: bundles/main.md
+    - Person: bundles/person.md
+    - Report: bundles/report.md
+
+extra:
+  social:
+    - icon: fontawesome/brands/gitlab
+      link: https://gitlab.com/Chill-project
+    - icon: fontawesome/solid/comments
+      link: https://app.element.io/#/room/#chill-social-admin:matrix.org

docs/requirements.txt

@@ -1,7 +1,4 @@
-docutils==0.13.1
-Pygments==2.2.0
-sphinx==1.8.5
-Jinja2<3.1
-git+https://github.com/fabpot/sphinx-php.git@v2.0.2#egg_name=sphinx-php
-jsx-lexer===0.0.8
-sphinx_rtd_theme==0.5.0
+mkdocs>=1.5.0
+mkdocs-material>=9.4.0
+pymdown-extensions>=10.3.0
+mkdocs-autorefs>=0.5.0

docs/source/_static/bundles/docStore/doc_store_classes.puml

@@ -23,8 +23,8 @@ class "Document" {
     - text description
     - ArrayCollection_DocumentCategory categories
     - varchar_150 content #link to openstack
-    - Center center
-    - Cercle cercle
+    - Territoire territoire
+    - Service service
     - User user
     - DateTime date # Creation date
 }

docs/source/_static/code/exports/BirthdateFilter.php

@@ -12,6 +12,7 @@ declare(strict_types=1);
 namespace Chill\PersonBundle\Export\Filter;
 
 use Chill\MainBundle\Export\ExportElementValidatedInterface;
+use Chill\MainBundle\Export\ExportGenerationContext;
 use Chill\MainBundle\Export\FilterInterface;
 use DateTime;
 use Doctrine\ORM\Query\Expr;
@@ -20,6 +21,7 @@ use Symfony\Component\Validator\Context\ExecutionContextInterface;
 
 class BirthdateFilter implements ExportElementValidatedInterface, FilterInterface
 {
+    use \Chill\MainBundle\Export\ExportDataNormalizerTrait;
     // add specific role for this filter
     public function addRole(): ?string
     {
@@ -28,7 +30,7 @@ class BirthdateFilter implements ExportElementValidatedInterface, FilterInterfac
     }
 
     // here, we alter the query created by Export
-    public function alterQuery(\Doctrine\ORM\QueryBuilder $qb, $data)
+    public function alterQuery(\Doctrine\ORM\QueryBuilder $qb, $data, \Chill\MainBundle\Export\ExportGenerationContext $exportGenerationContext): void
     {
         $where = $qb->getDQLPart('where');
         // we create the clause here
@@ -52,13 +54,13 @@ class BirthdateFilter implements ExportElementValidatedInterface, FilterInterfac
     }
 
     // we give information on which type of export this filter applies
-    public function applyOn()
+    public function applyOn(): string
     {
         return 'person';
     }
 
     // we build a form to collect some parameters from the users
-    public function buildForm(\Symfony\Component\Form\FormBuilderInterface $builder)
+    public function buildForm(\Symfony\Component\Form\FormBuilderInterface $builder): void
     {
         $builder->add('date_from', DateType::class, [
             'label' => 'Born after this date',
@@ -74,6 +76,18 @@ class BirthdateFilter implements ExportElementValidatedInterface, FilterInterfac
             'format' => 'dd-MM-yyyy',
         ]);
     }
+    public function getNormalizationVersion(): int
+    {
+        return 1;
+    }
+    public function normalizeFormData(array $formData): array
+    {
+        return ['date_from' => $this->normalizeDate($formData['date_from']), 'date_to' => $this->normalizeDate($formData['date_to'])];
+    }
+    public function denormalizeFormData(array $formData, int $fromVersion): array
+    {
+        return ['date_from' => $this->denormalizeDate($formData['date_from']), 'date_to' => $this->denormalizeDate($formData['date_to'])];
+    }
     public function getFormDefaultData(): array
     {
         return ['date_from' => new DateTime(), 'date_to' => new DateTime()];
@@ -81,7 +95,7 @@ class BirthdateFilter implements ExportElementValidatedInterface, FilterInterfac
 
     // here, we create a simple string which will describe the action of
     // the filter in the Response
-    public function describeAction($data, $format = 'string')
+    public function describeAction($data, ExportGenerationContext $context): string|\Symfony\Contracts\Translation\TranslatableInterface|array
     {
         return ['Filtered by person\'s birtdate: '
             . 'between %date_from% and %date_to%', [
@@ -90,7 +104,7 @@ class BirthdateFilter implements ExportElementValidatedInterface, FilterInterfac
             ], ];
     }
 
-    public function getTitle()
+    public function getTitle(): string|\Symfony\Contracts\Translation\TranslatableInterface
     {
         return 'Filter by person\'s birthdate';
     }
@@ -99,7 +113,7 @@ class BirthdateFilter implements ExportElementValidatedInterface, FilterInterfac
     // is executed here. This function is added by the interface
     // `ExportElementValidatedInterface`, and can be ignore if there is
     // no need for a validation
-    public function validateForm($data, ExecutionContextInterface $context)
+    public function validateForm($data, ExecutionContextInterface $context): void
     {
         $date_from = $data['date_from'];
         $date_to = $data['date_to'];

docs/source/_static/code/exports/CountPerson.php

@@ -36,6 +36,18 @@ class CountPerson implements ExportInterface
     {
         // this export does not add any form
     }
+    public function getNormalizationVersion(): int
+    {
+        return 1;
+    }
+    public function normalizeFormData(array $formData): array
+    {
+        return [];
+    }
+    public function denormalizeFormData(array $formData, int $fromVersion): array
+    {
+        return [];
+    }
     public function getFormDefaultData(): array
     {
         return [];
@@ -60,29 +72,29 @@ class CountPerson implements ExportInterface
         };
     }
 
-    public function getQueryKeys($data)
+    public function getQueryKeys($data): array
     {
         // this array match the result keys in the query. We have only
         // one column.
         return ['export_result'];
     }
 
-    public function getResult($query, $data)
+    public function getResult($query, $data, \Chill\MainBundle\Export\ExportGenerationContext $context): array
     {
         return $query->getQuery()->getResult(Query::HYDRATE_SCALAR);
     }
 
-    public function getTitle()
+    public function getTitle(): string|\Symfony\Contracts\Translation\TranslatableInterface
     {
         return 'Count peoples';
     }
 
-    public function getType()
+    public function getType(): string
     {
         return Declarations::PERSON_TYPE;
     }
 
-    public function initiateQuery(array $requiredModifiers, array $acl, array $data = [])
+    public function initiateQuery(array $requiredModifiers, array $acl, array $data, \Chill\MainBundle\Export\ExportGenerationContext $context): \Doctrine\ORM\QueryBuilder
     {
         // we gather all center the user choose.
         $centers = array_map(static fn ($el) => $el['center'], $acl);

docs/source/bundles/activity.md

@@ -0,0 +1,55 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# Activity bundle
+
+This bundle provides the ability to record people in the software. This bundle is required by other bundle.
+
+   :local:
+
+###### Entities provided
+
+   Describe the entities provided.
+
+###### Configuration options
+
+Those options are available under `chill_activity` key.
+
+Example of configuration:
+
+   chill_activity:
+      form:
+         time_duration:
+            - { label: '12 minutes', seconds: 720 }
+            - { label: '30 minutes', seconds: 1800 }
+
+form.time_duration *array*
+   The duration which might be suggested when the user create or update an activity. The value must be an array of object, where each object must have a `label` and a `seconds` key. The label provide which is shown to user (the label will be translated, if possible) and the seconds the duration.
+
+   Example: see the example above
+
+   Default value: the values available are 5, 10, 15, 20, 25, 30, 45 minutes, and 1 hour, 1 hour 15, 1 hour 30, 1 hour 45 and 2 hours.
+
+###### Macros
+
+## Activity reason sticker
+
+Macro file
+   `ChillActivityBundle:ActivityReason:macro.html.twig`
+Macro envelope
+   `reason(r)`
+
+   `p` is an instance of :class:`Chill\ActivityBundle\Entity\ActivityReason`
+
+When to use this macro ?
+   When you want to represent an activity reason.
+Example usage :
+   ```jinja
+   {% import 'ChillActivityBundle:ActivityReason:macro.html.twig' as m %}
+
+   {{ m.reason(r) }}
+   ```

docs/source/bundles/custom-fields.md

@@ -0,0 +1,381 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+   
+
+## Custom fields bundle
+
+This bundle provides the ability to add custom fields to existing entities.
+
+Those custom fields contains extra data and will be stored in the DB, along with other data's entities. It may be string, text, date, ... or a link to an existing entities.
+
+In the database, custom fields are stored in json format.
+
+   The full specification discussed [here. ](https://redmine.champs-libres.coop/issues/239)
+   
+   [JSON Type on postgresql documentation ](http://www.postgresql.org/docs/9.3/static/datatype-json.html)
+      The documentation of json type, which is used to store data in the database.
+   
+
+   :depth: 4
+   :local:
+
+### Custom Fields concepts
+
+Custom fields are extra data which may be added to entities by user. If a developer implements custom fields on a entity, users will be able to add more fields on this entity.
+
+Example: the [person bundle` allows to record `firstname`, `lastname`, `date of birth` fields. But users need to store information about the kind of house he has (if he owns his house, if he rents it, ...). Custom fields allows to create those fields.
+
+Automatically, those fields are added at the person form. They are also printed in the person view and in exports.
+
+##### Custom fields and custom fields group
+
+Custom fields are associated to a custom fields group. When a user want to add custom fields on an entity, he must first create a custom fields group and associate this field with an entity. Then he may add add custom fields to this groups. 
+
+Some entities needs a **default** custom fields group. For instance, the default custom fields group will be printed on the main form for person, and will be appended on the main person view. Some bundle does not use this feature (i.e. the `report` bundle).
+
+   In the future of the `person bundle`, other custom fields group will be added in forms accessible from the menu, allowing users to completely customize and separate their entities.
+   
+### Allow custom fields on an entity
+
+As a developer, you must allow your users to add custom fields on your entities.
+
+    For having custom fields, the class of the entity must contain a variable for storing the custom data. **By convention this variable must be called $cFData**
+
+##### Create a json field on your entity
+
+Declare a json field in your database :
+
+   Chill\CustomFieldsBundle\Entity\BlopEntity:
+      type: entity
+      # ...
+      fields:
+         cFData:
+            type: json_array
+            
+Create the field accordingly in the class logic :
+
+   namespace Chill\CustomFieldsBundle\Entity;
+   
+   /**
+   * BlopEntity
+   */
+   class BlopEntity
+   {
+   
+   /**
+   * @var array
+   */
+   private $cFData;
+   
+   /**
+   * You must set a setter in order to save automatically custom 
+   * fields from forms, using Form Component
+   *
+   * @param array $cFData
+   * @return BlopEntity
+   */
+   public function setCFData(array $cFData)
+   {
+      $this->cFData = $cFData;
+      return $this;
+   }
+   
+   /**
+   * You also must create a getter in order to let Form 
+   * component populate form fields
+   *
+   * @return array
+   */
+   public function getCFData()
+   {
+      return $this->cFData;
+   }
+            
+##### Declare your customizable entity in configuration
+
+This step is necessary to allow user to create custom fields group associated with this entity.
+
+Two methods are available.
+
+The recommended method is to do it in DependencyInjection/Extension class. It is recommended as your bundle will be well set up (for custom field) in every chill installation that use it.
+
+The discouraged method is to declare via the app/config.yml file. This is very quick to set up for a given chill installation but it is not done automatically : in every chill installation that use your bundle, this step has to be performed.
+
+In app/config.yml file (discouraged)
+""""""""""""""""""""""""""""""""""""
+
+This method is discouraged but explained first as it helps to undersand the recommended method.
+
+Add those file under `chill_custom_fields` section :
+
+   chill_custom_fields:
+      customizables_entities:
+         - { class: Chill\YourBundleBundle\Entity\BlopEntity, name: blop_entity }
+         
+* The `name` allow you to define a string which is translatable. This string will appears when chill's admin will add/retrieve new customFieldsGroup.
+* The class, which is a full FQDN class path
+
+Automatically, in DependencyInjection/Extension class (recommended)
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+This is the recommended way for declaring customizable classes. 
+
+You can prepend configuration of `custom fields bundle` from the class `YourBundle\DependencyInjection\YourBundleExtension`. **Note** that you also have to implements `Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface` on this class to make the `prepend` function being taken into account.
+
+Example here : 
+
+    class ChillYourBundleExtension extends Extension implements PrependExtensionInterface
+    {
+        /**
+         * @param ContainerBuilder $container
+         */
+        public function prepend(ContainerBuilder $container)
+        {
+            $bundles = $container->getParameter('kernel.bundles');
+            if (!isset($bundles['ChillCustomFieldsBundle'])) {
+                throw new MissingBundleException('ChillCustomFieldsBundle');
+            }
+
+            $container->prependExtensionConfig('chill_custom_fields',
+                array('customizables_entities' => 
+                    array(
+                        array(
+                            'class' => 'Chill\YourBundleBundle\Entity\BlopEntity', 
+                            'name' => 'blop_entity',)
+                   )
+               )
+            );
+        }
+    }
+
+* The `name` allow you to define a string which is translatable. This string will appears when chill's admin will add/retrieve new customFieldsGroup.
+* The class, which is a full FQDN class path
+
+   `How to simplify configuration of multiple bundles ](http://symfony.com/doc/current/cookbook/bundles/prepend_extension.html)
+      A cookbook page about prepending configuration.
+
+##### Adding options to your custom fields groups
+
+You may add options to the groups associated with an entity.
+
+In `config.yml` the declaration should be : 
+
+   chill_custom_fields:
+       customizables_entities:
+           - 
+               class: Chill\YourBundleBundle\Entity\BlopEntity
+               name: BlopEntity
+               options:
+                   # this will create a "myFieldKey" field as text, with a maxlength attribute to 150 (see http://symfony.com/doc/master/reference/forms/types/text.html)
+                   myFieldKey: {form_type: text, form_options: {attr: [maxlength: 150]}} 
+
+In the `PrependExtensionInterface::prepend` function, the options key will be added in the configuration definition : 
+
+   class ChillYourBundleExtension extends Extension implements PrependExtensionInterface
+   {
+       /**
+        * @param ContainerBuilder $container
+        */
+       public function prepend(ContainerBuilder $container)
+       {
+           $bundles = $container->getParameter('kernel.bundles');
+           if (!isset($bundles['ChillCustomFieldsBundle'])) {
+               throw new MissingBundleException('ChillCustomFieldsBundle');
+           }
+
+           $container->prependExtensionConfig('chill_custom_fields',
+               array('customizables_entities' => 
+                   array(
+                       array(
+                          'class' => 'Chill\YourBundleBundle\Entity\BlopEntity', 
+                          'name' => 'BlopEntity',
+                          'options' => array(
+                                'myFieldKey' => [ 'form_type' => 'text', 'form_options' => [ 'attr' => [ 'maxlength' => 150 ] ]
+                          ))
+                   )
+               )
+           );
+       }
+   }
+               
+**Example :** the entity `Report` from **ReportBundle** has to pick some custom fields belonging to a group to print them in *summaries* the timeline page. The definition will use the special type `custom_fields_group_linked_custom_field` which will add a select input with all fields associated with the current custom fields group : 
+
+   class ChillReportExtension extends Extension implements PrependExtensionInterface
+   {
+       /**
+###### *
+        * @param ContainerBuilder $container
+        */
+       public function prepend(ContainerBuilder $container)
+       {
+           $bundles = $container->getParameter('kernel.bundles');
+           if (!isset($bundles['ChillCustomFieldsBundle'])) {
+               throw new MissingBundleException('ChillCustomFieldsBundle');
+           }
+
+           $container->prependExtensionConfig('chill_custom_fields',
+               array('customizables_entities' => 
+                   array(
+                       array(
+                          'class' => 'Chill\ReportBundle\Entity\Report', 
+                          'name' => 'ReportEntity',
+                          'options' => array(
+                             'summary_fields' => array(
+                                'form_type' => 'custom_fields_group_linked_custom_fields',
+                                'form_options' => 
+                                   [
+                                      'multiple' => true,
+                                      'expanded' => false
+                                   ]
+                             )
+                          ))
+                   )
+               )
+           );
+       }
+   }
+
+Note that `custom_fields_group_linked_custom_fields` does not create any input on `CustomFieldsGroup` creation : there aren't any fields associated with the custom fields just after the group creation... You have to add custom fields and associate them with the newly created group to see them appears.
+
+### Rendering custom fields and custom fields group in a template
+
+    Each custom field can be `active` or not. Only `active` custom fields has to be dislayed.
+
+For rendering custom fields, two function are available :
+
+* `chill_custom_field_widget` to render the widget. This function is defined on a customFieldType basis.
+* `chill_custom_field_label` to render the label. You can customize the label rendering by choosing the layout you would like to use.
+* `chill_custom_field_is_empty` indicates if the content of the custom fields is empty (return a boolean)
+
+For rendering custom fields group, a function is available :
+
+* `chill_custom_fields_group_widget` to render the widget. It will display the custom fields of the group in a dd / dt structure.
+
+##### chill_custom_field_label
+
+The signature is :
+
+* `CustomField` **$customField** a customField instance
+* `array` **params** the parameters for rendering. Currently, 'label_layout' allow to choose a different label. Default is 'ChillCustomFieldsBundle:CustomField:render_label.html.twig'
+
+Examples
+
+   {{ chill_custom_field_label(customField) }}
+
+##### chill_custom_field_widget
+
+The signature is :
+
+*  array **$fields** the array raw, as stored in the db
+*  CustomField **$customField** a customField instance 
+*  string **$documentType** the type of document. Default to `html`.
+
+Examples:
+
+   {{ chill_custom_field_widget(entity.customFields, customField) }}
+
+##### chill_custom_field_is_empty
+
+The signature is :
+
+* array **$fields** the array raw, as stored in the db
+* CustomField **$customField** a customField instance
+
+Examples :
+
+   {%- if chill_custom_field_is_empty(cFData, customField) == false -%}
+
+##### chill_custom_fields_group_widget
+
+This function only display custom fields that are `active`.
+
+The signature is :
+
+*  array **$fields** the array raw, as stored in the db
+*  CustomFieldsGroup **$customFieldsGroup** the custom field group to render
+
+   {{ chill_custom_fields_group_widget(entity.cFData, entity.customFieldsGroup) }}
+
+### Custom Fields's form
+
+You should simply use the 'custom_field' type in a template, with the group you would like to render in the `group` option's type.
+
+Example : 
+
+   namespace Chill\ReportBundle\Form;
+
+   use Symfony\Component\Form\AbstractType;
+   use Symfony\Component\Form\FormBuilderInterface;
+   use Symfony\Component\OptionsResolver\OptionsResolverInterface;
+
+   class ReportType extends AbstractType
+   {
+       /**
+        * @param FormBuilderInterface $builder
+        * @param array $options
+        */
+       public function buildForm(FormBuilderInterface $builder, array $options)
+       {
+           $entityManager = $options['em'];
+
+           $builder
+               ->add('user')
+               ->add('date', 'date', 
+                   array('required' => true, 'widget' => 'single_text', 'format' => 'dd-MM-yyyy'))
+               #add the custom fields :
+               ->add('cFData', 'custom_field', 
+                   array('attr' => array('class' => 'cf-fields'), 'group' => $options['cFGroup']))
+           ;
+       }
+       
+       /**
+        * @param OptionsResolverInterface $resolver
+        */
+       public function setDefaultOptions(OptionsResolverInterface $resolver)
+       {
+           $resolver->setDefaults(array(
+               'data_class' => 'Chill\ReportBundle\Entity\Report'
+           ));
+
+           $resolver->setRequired(array(
+               'em',
+               'cFGroup',
+           ));
+
+           $resolver->setAllowedTypes(array(
+               'em' => 'Doctrine\Common\Persistence\ObjectManager',
+               'cFGroup' => 'Chill\CustomFieldsBundle\Entity\CustomFieldsGroup'
+           ));
+       }
+
+       /**
+        * @return string
+        */
+       public function getName()
+       {
+           return 'chill_reportbundle_report';
+       }
+   }
+
+### Available configuration
+
+Those options are available in the configuration, under the `chill_custom_field` key.
+
+Example :
+
+   chill_custom_field:
+      show_empty_values_in_views:  false
+
+show_empty_values_in_views *boolean*:
+   Allow to hide / show empty values in views. The aim of this configuration parameter is to hide (or show) empty values when :term:`custom fields group` are rendered.
+
+   Default value : `true`
+
+### Glossary
+
+   custom fields group
+      A group of custom fields

docs/source/bundles/event.md

@@ -0,0 +1,23 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# Event bundle
+
+## Template & Menu
+
+The event bundle has a special template with a specific menu for actions on
+events. This menu is called `event`.
+
+### ChillEventBundle::layout.html.twig
+
+This layout extends `ChillMainBundle::layoutWithVerticalMenu.html.twig` and add the menu `event`
+
+It proposes a new block :
+
+* event_content
+
+  * where to display content relative to the event.

docs/source/bundles/group.md

@@ -0,0 +1,34 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# Group bundle
+
+Allow to group people in a group. This group may be a family, an activity group, ...
+
+   :local:
+
+###### Entities
+
+###### Macros
+
+## Group sticker
+
+Macro file
+   `ChillGroupBundle:Group:macro.html.twig`
+Macro name
+   `_render`
+Macro envelope
+   `group`, instance of :class:`Chill\GroupBundle\Entity\CGroup`
+
+When to use this macro ?
+   When you want to represent group.
+Example usage :
+   ```jinja
+   {% import 'ChillGroupBundle:Group:macro.html.twig' as m %}
+
+   {{ m._render(g) }}
+   ```

docs/source/bundles/index.md

@@ -0,0 +1,23 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# Bundles documentation
+
+You will find here documentation about bundles working with Chill.
+
+- [Main bundle](main.md)
+- [Custom Fields bundle](custom-fields.md)
+- [Person bundle](person.md)
+- [Report bundle](report.md)
+- [Activity bundle](activity.md)
+- [Group bundle](group.md)
+- [Event bundle](event.md)
+- [Ldap bundle (synchronisation between ldap and database)](ldap.md)
+
+### Your bundle here ?
+
+The contributors still do not have a policy about those bundle integration, but we would like to be very open on this subject. Please write to us [or open an issue ](https://redmine.champs-libres.coop/projects/chill/issues).

docs/source/bundles/ldap.md

@@ -0,0 +1,159 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# LDAP bundle
+
+This bundle binds the database with an ldap directory.
+
+The bundle synchronize the ldap directory with users in the database. It also
+provides a way to check user credentials against the ldap directory.
+
+   :local:
+
+###### Current limitations
+
+- The length of the ldap dn must be < 255 characters
+- if the username extracted from the ldap is updated, the changes are not reflected in the database and remains the same
+
+###### Entities provided
+
+This bundle provides only one entity : :class:[Chill\\LdapBundle\\Entity\\UserLdapBinding`
+
+###### How the synchronizer works ?
+
+#. The synchronizer performs a query on `dn` and `query` defined in the [configuration ](configuration.md).
+#. For each entry returned by the query, it looks if the `dn` exists in the database
+
+   #. If the entry does not exists :
+
+      #. the synchronizer looks for user with same username as defined by `username_attr`, and bind it with the `dn` if it exists.
+      #. else, a user is created with username defined by `username_attr` (if the ldap contains more than one attribute, the first attribute returned is used)
+
+   #. if a user exists which is already binded with the `dn`, the entry is ignored.
+
+#. The synchronizer looks for dn existing in database and which were not returned by the query performed in 1.
+
+   #. If they exists, those user are set to `enabled=false`: they are not allowed to login.
+
+###### Installation
+
+This bundle requires :
+
+- PHP LDAP ext
+- `symfony/ldap` with minimal version 3.1. Note that, currently, Chill uses Symfony 2.8: you should add the dependency on this single package manually
+
+In your composer.json, for stable version :
+
+   "require": {
+           // .. other dependencies
+           "symfony/ldap" : "~3.1",
+           "chill-project/ldap": "~1.0"
+   }
+
+And for dev version :
+
+   "require": {
+           // .. other dependencies
+           "symfony/ldap" : "~3.1",
+           "chill-project/ldap": "dev-master@dev"
+   }
+
+###### Configuration
+
+## Configuration of the bundle
+
+   # Default configuration for extension with alias: "chill_ldap"
+   chill_ldap:
+       server:               # Required
+
+           # the host of the ldap directory
+           host:                 ~ # Required, Example: localhost
+
+           # the port to reach the ldap directory
+           port:                 389
+
+           # the version of the ldap directory
+           version:              3
+
+           # Is the use of ssl required to establish connection
+           use_ssl:              false
+
+           # Is the use of startssl required to establish connection
+           use_starttls:         false
+
+           # the user to bind to dn directory. Required for searching existing users.
+           bind_dn:              ~ # Required, Example: cn=user,dn=chill,dn=social
+
+           # the user's password to bind to dn directory.
+           bind_password:        ~ # Required, Example: paSSw0rD
+       user_query:           # Required
+
+           # The DN where the query is executed
+           dn:                   ~ # Example: ou=People,dc=champs-libres,dc=coop
+
+           # The query which will allow to retrieve users
+           query:                ~ # Example: (&(objectClass=inetOrgPerson)(userPassword=*))
+
+           # The attribute which will provide username (=login)
+           username_attr:        cn
+
+Example :
+
+   chill_ldap:
+       server:
+           # host, bind_dn and bind_password are imported from parameters.yml
+           host: "%ldap_host%"
+           bind_dn: "%ldap_bind_dn%"
+           bind_password: "%ldap_bind_password%"
+       user_query:
+           dn: dc=champs-libres,dc=coop
+           query: "(&(objectClass=inetOrgPerson)(userPassword=*))"
+
+## Configuration of the security part of chill
+
+Simply add the following config in the firewall of the security bundle :
+`chill_ldap_form_login: ~`. This config is located in `app/config/security.yml`
+
+Example of a configuration :
+
+   # in app/config/security.yml
+
+       firewalls:
+           dev:
+               pattern: ^/(_(profiler|wdt)|css|images|js)/
+               security: false
+
+           default:
+               anonymous: ~
+               # enable the login check by a form, agaisnt the database
+               form_login:
+                   csrf_parameter: _csrf_token
+                   csrf_token_id: authenticate
+                   csrf_provider: form.csrf_provider
+               # enable the login check by a form, against the ldap
+               chill_ldap_form_login: ~ # this is the line you should add
+
+Note that, if you enable the login check by form **and** by the ldap,
+the password will be checked against the database **and** against the ldap.
+If one of them match, the login will succeed.
+
+If you want to completely disable login check against the database,
+simply remove the `form_login` entry and all his options.
+
+## Command and crontab
+
+Synchronize the database :
+
+   php app/console chill:ldap:synchronize
+
+For getting more debug message :
+
+   php app/console chill:ldap:synchronize -vvv
+
+You should run this command regularly (using crontab or
+`systemd timer ](https://www.freedesktop.org/software/systemd/man/systemd.timer.html#))
+to synchronize ldap and database automatically.

docs/source/bundles/main.md

@@ -0,0 +1,38 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+
+# Main bundle
+
+This bundle is **required** for running Chill.
+
+This bundle provide :
+
+* Access control model (users, groups, and all concepts)
+* ...
+
+   this section is incomplete.
+
+###### Macros
+
+## Address sticker
+
+Macro file
+   `ChillMainBundle:Address:macro.html.twig`
+Macro name
+   `_render`
+Macro envelope
+   `address`, instance of :class:`Chill\MainBundle\Entity\Address`
+
+When to use this macro ?
+   When you want to represent an address.
+Example usage :
+   ```jinja
+   {% import 'ChillMainBundle:Address:macro.html.twig' as m %}
+
+   {{ m._render(address) }}
+   ```

docs/source/bundles/person.md

@@ -0,0 +1,196 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# Person bundle
+
+This bundle provides the ability to record people in the software. This bundle is required by other bundle.
+
+   :local:
+
+###### Entities provided
+
+   describe entities provided by person bundle
+
+
+###### Search terms
+
+The class [Chill\PersonBundle\Search\PersonSearch` provide the search module.
+
+## Domain
+
+The search upon "person" is provided by default. The `@person` domain search may be omitted.
+
+* `@person` is the domain search for people.
+
+## Arguments
+
+* `firstname` : provide the search on firstname. Example : `firstname:Depardieu`. May match part of the firstname (`firsname:dep` will match Depardieu)
+* `lastname` : provide the search on lastname. May match part of the lastname.
+* `birthdate` : provide the search on the birthdate. Example : `birthdate:1996-01-19`
+* `gender`: performs search on man/woman. The accepted values are `man` or `woman`.
+* `nationality` : performs search on nationality. Value must be a country code `as described in ISO 3166 ](http://www.iso.org/iso/fr/home/standards/country_codes.htm). Example : [nationality:FR`.
+
+## Default
+
+The default search is performed on firstname and/or lastname. Both are concatened before search. If values are separated by spaces, the clause `AND` is used : the search `dep ge` will match 'Gérard Depardieu` or 'Jean Depagelles', but not 'Charline Depardieu' (missing 'Ge' in word).
+
+###### Configuration options
+
+Those options are available under `chill_person` key.
+
+Example of configuration:
+
+   chill_person:
+      validation:
+         birthdate_not_after: P15Y
+      person_fields:
+         # note: visible is the default config. This key may be omitted if visible is chosen.
+         nationality: hidden
+         email: hidden
+         place_of_birth: visible
+         phonenumber: hidden
+         country_of_birth: hidden
+         marital_status: visible
+         spoken_languages: hidden
+         address: visible
+
+birthdate_not_after *string*
+   The period duration before today during which encoding birthdate is not possible. The period is a string matching the format of `ISO_8601`, which is also use to build `DateInterval classes ](http://php.net/manual/en/dateinterval.construct.php).
+
+   Example: [P1D`, `P18Y`
+
+   Default value: `P1D` which means that birthdate before the current day (= yesterday) are allowed.
+
+person_fields *array*
+   This define the visibility of some fields. By default, all fields are visible, but you can choose to hide some of them. Available keys are :
+
+   * `nationality`
+   * `country_of_birth`
+   * `place_of_birth`
+   * `phonenumber`
+   * `email`
+   * `marital_status`
+   * `spoken_languages`
+   * `address`
+
+   Possibles values: `hidden` or `visible` (all other value will raise an Exception).
+
+   Default value : `visible`, which means that all fields are visible.
+
+   Example:
+
+   ```yaml
+      chill_person:
+         person_fields:
+            nationality: hidden
+            email: hidden
+            phonenumber: hidden
+```
+
+   If all the field of a "box" are hidden, the whole box does not appears. Example: if the fields `phonenumber` and `email` are hidden, the title `Contact information` will be hidden in the UI.
+
+   If you hide multiple fields, for a better integration you may want to override the template, for a better appeareance. See `the symfony documentation ](http://symfony.com/doc/current/book/templating.html#overriding-bundle-templates) about this feature.
+
+###### Macros
+
+## Sticker for a person
+
+Macro file
+   `ChillPersonBundle:Person:macro.html.twig`
+Macro envelope
+   `render(p, withLink=false)`
+
+   `p` is an instance of :class:`Chill\PersonBundle\Entity\Person`
+
+   `withLink` :class:`boolean`
+When to use this macro ?
+   When you want to represent a person.
+Example usage :
+   ```jinja
+   {% import "ChillPersonBundle:Person:macro.html.twig" as person_ %}
+
+   {{ person_.render(person, true) }}
+   ```
+
+###### Layout events and delegated blocks
+
+## `chill_block.person_post_vertical_menu` event
+
+This event is available to add content below of the vertical menu (on the right).
+
+The context is :
+
+- `person` : the current person which is rendered. Instance of :class:`Chill\PersonBundle\Entity\Person`
+
+###### Widgets
+
+## Add a list of person on homepage
+
+The bundle provide a way to add a list of accompanyied person on the homepage:
+
+   chill_main:
+       widgets:
+           homepage:
+               -
+                   order: 10
+                   widget_alias: person_list
+                   person_list:
+                       # customize the number of items
+                       number_of_items: 20
+
+                       # only active
+                       only_active: true
+
+                       # you can add some filtering class, which will implements
+                       # Chill\PersonBundle\PersonListWidget\PersonFilteringInterface
+                       filtering_class: "\Hepc\HomepagePersonFiltering"
+
+                       # when the view is overriden, you can add some custom fields
+                       # to the view
+                       custom_fields: [school-2fb5440e-192c-11e6-b2fd-74d02b0c9b55]
+
+###### Commands
+
+## `chill:person:move`
+
+	Usage:
+		chill:person:move [options]
+
+	Options:
+		-f, --from=FROM       The person id to delete, all associated data will be moved before
+		-t, --to=TO           The person id which will received data
+				--dump-sql        dump sql to stdout
+				--force           execute sql instead of dumping it
+		-h, --help            Display this help message
+		-q, --quiet           Do not output any message
+		-V, --version         Display this application version
+				--ansi            Force ANSI output
+				--no-ansi         Disable ANSI output
+		-n, --no-interaction  Do not ask any interactive question
+		-e, --env=ENV         The Environment name. [default: "dev"]
+				--no-debug        Switches off debug mode.
+		-v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
+
+	Help:
+		Move all the associated entities on a "from" person to a "to" person and remove the old person
+
+Move all the entities associated to a person onto another one, and remove the old person.
+
+  Some entities are ignored and will be deleted:
+
+  - the accompanying periods ;
+  - the data attached to a person entity: name, address, date of birth, etc. Thos should be merge before the move.
+
+It is advised to run first the command with the `dump-sql` option and, then, use the `force` option.
+
+The moving and suppression is executed inside a transaction, ensuring no data loss if the migration fails.
+
+  Using bash and awk, it is easy to use a TSV file (values separated by a tab, not a comma) to create move commands. Assuming our file is named `twins.tsv` and contains two columns: the first one with `from` ids, and the second one with `to` ids:
+
+  ```bash
+    awk '{ print "php app/console chill:person:move --dump-sql --from " $1 " --to " $2;}' twins.tsv
+```

docs/source/bundles/report.md

@@ -0,0 +1,32 @@
+Permission is granted to copy, distribute and/or modify this document
+   under the terms of the GNU Free Documentation License, Version 1.3
+   or any later version published by the Free Software Foundation;
+   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+   A copy of the license is included in the section entitled "GNU
+   Free Documentation License".
+
+# Report bundle
+
+This bundle provides the ability to record report about people. We use custom fields to let user add fields to reports.
+
+   :local:
+
+   The documentation about report is not writtend
+
+## Concepts
+
+## Search
+
+### Domain
+
+* `@report` is the domain search for reports.
+
+### Arguments
+
+* `date` : The date of the report
+
+### Default
+
+The report's date is the default value. 
+
+An error is thrown if an argument `date` and a default is used.

docs/source/bundles/rst/activity.rst

@@ -35,12 +35,12 @@ Example of configuration:
 
    chill_activity:
       form:
-         time_duration: 
+         time_duration:
             - { label: '12 minutes', seconds: 720 }
             - { label: '30 minutes', seconds: 1800 }
 
 form.time_duration *array*
-   The duration which might be suggested when the user create or update an activity. The value must be an array of object, where each object must have a :code:`label` and a :code:`seconds` key. The label provide which is shown to user (the label will be translated, if possible) and the seconds the duration.
+   The duration which might be suggested when the user create or update an activity. The value must be an array of object, where each object must have a `label` and a `seconds` key. The label provide which is shown to user (the label will be translated, if possible) and the seconds the duration.
 
    Example: see the example above
 
@@ -57,9 +57,9 @@ Activity reason sticker
 Macro file
    `ChillActivityBundle:ActivityReason:macro.html.twig`
 Macro envelope
-   :code:`reason(r)`
+   `reason(r)`
 
-   :code:`p` is an instance of :class:`Chill\ActivityBundle\Entity\ActivityReason`
+   `p` is an instance of :class:`Chill\ActivityBundle\Entity\ActivityReason`
 
 When to use this macro ?
    When you want to represent an activity reason.

docs/source/bundles/rst/group.rst

@@ -33,9 +33,9 @@ Group sticker
 Macro file
    `ChillGroupBundle:Group:macro.html.twig`
 Macro name
-   :code:`_render`
+   `_render`
 Macro envelope
-   :code:`group`, instance of :class:`Chill\GroupBundle\Entity\CGroup`
+   `group`, instance of :class:`Chill\GroupBundle\Entity\CGroup`
 
 When to use this macro ?
    When you want to represent group.

docs/source/bundles/rst/ldap.rst

@@ -35,34 +35,34 @@ This bundle provides only one entity : :class:`Chill\\LdapBundle\\Entity\\UserLd
 How the synchronizer works ?
 ****************************
 
-#. The synchronizer performs a query on :code:`dn` and :code:`query` defined in the :ref:`configuration <configuration>`.
-#. For each entry returned by the query, it looks if the :code:`dn` exists in the database
+#. The synchronizer performs a query on `dn` and `query` defined in the :ref:`configuration <configuration>`.
+#. For each entry returned by the query, it looks if the `dn` exists in the database
 
    #. If the entry does not exists :
 
-      #. the synchronizer looks for user with same username as defined by :code:`username_attr`, and bind it with the :code:`dn` if it exists.
-      #. else, a user is created with username defined by :code:`username_attr` (if the ldap contains more than one attribute, the first attribute returned is used)
+      #. the synchronizer looks for user with same username as defined by `username_attr`, and bind it with the `dn` if it exists.
+      #. else, a user is created with username defined by `username_attr` (if the ldap contains more than one attribute, the first attribute returned is used)
 
-   #. if a user exists which is already binded with the :code:`dn`, the entry is ignored.
+   #. if a user exists which is already binded with the `dn`, the entry is ignored.
 
-#. The synchronizer looks for dn existing in database and which were not returned by the query performed in 1. 
+#. The synchronizer looks for dn existing in database and which were not returned by the query performed in 1.
 
-   #. If they exists, those user are set to :code:`enabled=false`: they are not allowed to login.
+   #. If they exists, those user are set to `enabled=false`: they are not allowed to login.
 
 Installation
 ************
 
-This bundle requires : 
+This bundle requires :
 
 - PHP LDAP ext
-- :code:`symfony/ldap` with minimal version 3.1. Note that, currently, Chill uses Symfony 2.8: you should add the dependency on this single package manually
+- `symfony/ldap` with minimal version 3.1. Note that, currently, Chill uses Symfony 2.8: you should add the dependency on this single package manually
 
-In your composer.json, for stable version : 
+In your composer.json, for stable version :
 
 .. code-block:: json
 
    "require": {
-           // .. other dependencies 
+           // .. other dependencies
            "symfony/ldap" : "~3.1",
            "chill-project/ldap": "~1.0"
    }
@@ -74,7 +74,7 @@ And for dev version :
 .. code-block:: json
 
    "require": {
-           // .. other dependencies 
+           // .. other dependencies
            "symfony/ldap" : "~3.1",
            "chill-project/ldap": "dev-master@dev"
    }
@@ -126,7 +126,7 @@ Configuration of the bundle
            username_attr:        cn
 
 
-Example : 
+Example :
 
 .. code-block:: yaml
 
@@ -147,7 +147,7 @@ Configuration of the security part of chill
 Simply add the following config in the firewall of the security bundle :
 `chill_ldap_form_login: ~`. This config is located in `app/config/security.yml`
 
-Example of a configuration : 
+Example of a configuration :
 
 .. code-block:: yaml
 
@@ -169,26 +169,26 @@ Example of a configuration :
                chill_ldap_form_login: ~ # this is the line you should add
 
 
-Note that, if you enable the login check by form **and** by the ldap, 
+Note that, if you enable the login check by form **and** by the ldap,
 the password will be checked against the database **and** against the ldap.
 If one of them match, the login will succeed.
 
-If you want to completely disable login check against the database, 
-simply remove the :code:`form_login` entry and all his options.
+If you want to completely disable login check against the database,
+simply remove the `form_login` entry and all his options.
 
 .. _command-and-crontab:
 
 Command and crontab
 ===================
 
-Synchronize the database : 
+Synchronize the database :
 
 .. code-block:: bash
 
    php app/console chill:ldap:synchronize
 
 
-For getting more debug message : 
+For getting more debug message :
 
 .. code-block:: bash
 
@@ -196,7 +196,7 @@ For getting more debug message :
 
 
 
-You should run this command regularly (using crontab or 
+You should run this command regularly (using crontab or
 `systemd timer <https://www.freedesktop.org/software/systemd/man/systemd.timer.html#>`_)
 to synchronize ldap and database automatically.
 

docs/source/bundles/rst/main.rst

@@ -7,7 +7,7 @@
    Free Documentation License".
 
 .. _main-bundle:
- 
+
 Main bundle
 ###########
 
@@ -34,9 +34,9 @@ Address sticker
 Macro file
    `ChillMainBundle:Address:macro.html.twig`
 Macro name
-   :code:`_render`
+   `_render`
 Macro envelope
-   :code:`address`, instance of :class:`Chill\MainBundle\Entity\Address`
+   `address`, instance of :class:`Chill\MainBundle\Entity\Address`
 
 When to use this macro ?
    When you want to represent an address.

docs/source/bundles/rst/person.rst

@@ -22,8 +22,8 @@ Entities provided
 .. todo::
 
    describe entities provided by person bundle
-   
-   
+
+
 Search terms
 ************
 
@@ -82,8 +82,8 @@ birthdate_not_after *string*
    Default value: `P1D` which means that birthdate before the current day (= yesterday) are allowed.
 
 person_fields *array*
-   This define the visibility of some fields. By default, all fields are visible, but you can choose to hide some of them. Available keys are : 
-   
+   This define the visibility of some fields. By default, all fields are visible, but you can choose to hide some of them. Available keys are :
+
    * `nationality`
    * `country_of_birth`
    * `place_of_birth`
@@ -97,7 +97,7 @@ person_fields *array*
 
    Default value : `visible`, which means that all fields are visible.
 
-   Example: 
+   Example:
 
    .. code-block:: yaml
 
@@ -107,10 +107,10 @@ person_fields *array*
             email: hidden
             phonenumber: hidden
 
-.. note:: 
+.. note::
    If all the field of a "box" are hidden, the whole box does not appears. Example: if the fields `phonenumber` and `email` are hidden, the title `Contact information` will be hidden in the UI.
 
-.. note:: 
+.. note::
    If you hide multiple fields, for a better integration you may want to override the template, for a better appeareance. See `the symfony documentation <http://symfony.com/doc/current/book/templating.html#overriding-bundle-templates>`_ about this feature.
 
 .. _person-bundle-macros:
@@ -124,11 +124,11 @@ Sticker for a person
 Macro file
    `ChillPersonBundle:Person:macro.html.twig`
 Macro envelope
-   :code:`render(p, withLink=false)`
+   `render(p, withLink=false)`
 
-   :code:`p` is an instance of :class:`Chill\PersonBundle\Entity\Person`
+   `p` is an instance of :class:`Chill\PersonBundle\Entity\Person`
 
-   :code:`withLink` :class:`boolean`
+   `withLink` :class:`boolean`
 When to use this macro ?
    When you want to represent a person.
 Example usage :
@@ -141,14 +141,14 @@ Example usage :
 Layout events and delegated blocks
 ***********************************
 
-:code:`chill_block.person_post_vertical_menu` event
+`chill_block.person_post_vertical_menu` event
 ====================================================
 
 This event is available to add content below of the vertical menu (on the right).
 
-The context is : 
+The context is :
 
-- :code:`person` : the current person which is rendered. Instance of :class:`Chill\PersonBundle\Entity\Person`
+- `person` : the current person which is rendered. Instance of :class:`Chill\PersonBundle\Entity\Person`
 
 Widgets
 *******
@@ -162,8 +162,8 @@ The bundle provide a way to add a list of accompanyied person on the homepage:
 
    chill_main:
        widgets:
-           homepage: 
-               - 
+           homepage:
+               -
                    order: 10
                    widget_alias: person_list
                    person_list:
@@ -180,12 +180,12 @@ The bundle provide a way to add a list of accompanyied person on the homepage:
                        # when the view is overriden, you can add some custom fields
                        # to the view
                        custom_fields: [school-2fb5440e-192c-11e6-b2fd-74d02b0c9b55]
-  
+
 Commands
 ********
 
 
-:code:`chill:person:move`
+`chill:person:move`
 =========================
 
 .. code-block:: txt
@@ -213,21 +213,21 @@ Commands
 
 Move all the entities associated to a person onto another one, and remove the old person.
 
-.. warning:: 
+.. warning::
 
-  Some entities are ignored and will be deleted: 
+  Some entities are ignored and will be deleted:
 
   - the accompanying periods ;
   - the data attached to a person entity: name, address, date of birth, etc. Thos should be merge before the move.
 
-It is advised to run first the command with the :code:`dump-sql` option and, then, use the :code:`force` option.
+It is advised to run first the command with the `dump-sql` option and, then, use the `force` option.
 
 The moving and suppression is executed inside a transaction, ensuring no data loss if the migration fails.
 
 .. note::
 
-  Using bash and awk, it is easy to use a TSV file (values separated by a tab, not a comma) to create move commands. Assuming our file is named :code:`twins.tsv` and contains two columns: the first one with :code:`from` ids, and the second one with :code:`to` ids: 
+  Using bash and awk, it is easy to use a TSV file (values separated by a tab, not a comma) to create move commands. Assuming our file is named `twins.tsv` and contains two columns: the first one with `from` ids, and the second one with `to` ids:
 
   .. code-block:: bash
 
-    awk '{ print "php app/console chill:person:move --dump-sql --from " $1 " --to " $2;}' twins.tsv 
+    awk '{ print "php app/console chill:person:move --dump-sql --from " $1 " --to " $2;}' twins.tsv

docs/source/development/FAQ.md

@@ -0,0 +1,23 @@
+# Frequently asked questions
+
+## Continuous integration
+
+Pipeline fails, but php-cs-fixer doesn't alert me when running it locally?
+========================================
+
+It is possible that you run php-cs-fixer on your local instance of chill and no fixes are made.
+Everything seems fine, so you push. However, once the pipeline is run in gitlab, you're notified that it failed due to php
+cs errors.
+
+In this case it's likely that you have to update your version of php-cs-fixer.
+php-cs-fixer is installed when building the docker image: https://gitea.champs-libres.be/Chill-project/chill-skeleton-basic/src/branch/main/Dockerfile#L50
+
+Consequently, to update php-cs-fixer, we have to update the image by building it again.
+
+For this the following commands can be used.
+
+```
+    docker compose build --pull php
+    # replace existing containers
+    docker compose up -d --force-recreate php
+```

docs/source/development/FAQ.rst

@@ -1,36 +0,0 @@
-.. Copyright (C)  2014 Champs Libres Cooperative SCRLFS
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3
-or any later version published by the Free Software Foundation;
-with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
-A copy of the license is included in the section entitled "GNU
-Free Documentation License".
-
-.. _faq:
-
-
-Frequently asked questions
-####################
-
-Continuous integration
-***********
-
-Pipeline fails, but php-cs-fixer doesn't alert me when running it locally ?
-========================================
-
-It is possible that you run php-cs-fixer on your local instance of chill and no fixes are made.
-Everything seems fine, so you push. However once the pipeline is run in gitlab, you're notified that it failed due to php
-cs errors.
-
-In this case it's likely that you have to update your version of php-cs-fixer.
-php-cs-fixer is installed when building the docker image: https://gitea.champs-libres.be/Chill-project/chill-skeleton-basic/src/branch/main/Dockerfile#L50
-
-Consequently, to update php-cs-fixer we have to update the image by building it again.
-
-For this the following commands can be used,
-
-.. code-block:: php
-
-    docker compose build --pull php
-    # replace existing containers
-    docker compose up -d --force-recreate php

docs/source/development/access_control_model.md

@@ -1,19 +1,15 @@
-.. Copyright (C)  2015 Champs Libres Cooperative SCRLFS
-   Permission is granted to copy, distribute and/or modify this document
+Permission is granted to copy, distribute and/or modify this document
    under the terms of the GNU Free Documentation License, Version 1.3
    or any later version published by the Free Software Foundation;
    with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
    A copy of the license is included in the section entitled "GNU
    Free Documentation License".
 
-Access controle model
-**********************
+###### Access controle model
 
-.. contents:: Table of content
     :local:
 
-Concepts
-========
+## Concepts
 
 Every time an entity is created, viewed or updated, the software check if the user has the permission to make this action. The decision is made with three parameters :
 
@@ -23,20 +19,15 @@ Every time an entity is created, viewed or updated, the software check if the us
 
 The user must be granted access to the action on this particular entity, with this scope and center.
 
-TL;DR
-=====
+## TL;DR
 
-Resolve scope and center
-------------------------
+### Resolve scope and center
 
 In a service, resolve the center and scope of an entity
 
-.. code-block:: php
-
    use Chill\MainBundle\Security\Resolver\CenterResolverDispatcher;
    use Chill\MainBundle\Security\Resolver\ScopeResolverDispatcher;
 
-
    class MyService {
       private ScopeResolverDispatcher $scopeResolverDispatcher;
       private CenterResolverDispatcher $centerResolverDispatcher;
@@ -58,8 +49,6 @@ In a service, resolve the center and scope of an entity
 
 In twig template, resolve the center:
 
-.. code-block:: twig
-
    {# resolve a center #}
 
    {% if person|chill_resolve_center is not null%}
@@ -81,8 +70,6 @@ In twig template, resolve the center:
 
 In twig template, resolve the scope:
 
-.. code-block:: twig
-
    {% if entity|chill_is_scope_concerned %}
 
       {% if entity|chill_resolve_scope is iterable %}
@@ -98,10 +85,7 @@ In twig template, resolve the scope:
       {% endfor %}
    {%- endif -%}
 
-Build a ``Voter``
------------------
-
-.. code-block:: php
+### Build a ``Voter``
 
    <?php
 
@@ -151,7 +135,6 @@ Build a ``Voter``
                ->build();
        }
 
-
        protected function supports($attribute, $subject)
        {
            return $this->voterHelper->supports($attribute, $subject);
@@ -194,25 +177,19 @@ Build a ``Voter``
            return array();
        }
 
-
        public function getRolesWithHierarchy()
        {
            return ['PersonDocument' => $this->getRoles() ];
        }
    }
 
-
-
-
-From an user point of view
-==========================
+## From an user point of view
 
 The software is design to allow fine tuned access rights for complicated installation and team structure. The administrators may also decide that every user has the right to see all resources, where team have a more simple structure. 
 
 Here is an overview of the model.
 
-Chill can be multi-center
--------------------------
+### Chill can be multi-center
 
 Chill is designed to be installed once for social center who work with multiple teams separated, or for social services's federation who would like to share the same installation of the software for all their members. 
 
@@ -222,8 +199,7 @@ Otherwise, it is not required to create multiple center: Chill can also work for
 
 Obviously, users working in the different centers are not allowed to see the entities (_persons_, _reports_, _activities_) of other centers. But users may be attached to multiple centers: consequently they will be able to see the entities of the multiple centers they are attached to.
 
-Inside center, scope divide team
---------------------------------
+### Inside center, scope divide team
 
 Users are attached to one or more center and, inside to those center, there may exists differents scopes. The aim of those _scopes_ is to divide the whole team of social worker amongst different departement, for instance: the social team, the psychologist team, the nurse team, the administrative team, ... Each team is granted of different rights amongst scope. For instance, the social team may not see the _activities_ of the psychologist team. The administrative team may see the date & time's activities, but is not allowed to see the detail of those entities (the personal notes, ...).
 
@@ -233,9 +209,7 @@ As entities have only one scopes, if some entities must be shared across two dif
 
 Example: if some activities must be seen and updated between nurses and psychologists, the administrator will create a scope "nurse and psy" and add the ability for both team "nurse" and "psychologist" to "create", "see", and "update" the activities belonging to scope "nurse and psy".
 
-
-Where does the ``scope`` and ``center`` comes from ?
-====================================================
+## Where does the [`scope`` and ``center`` comes from ?
 
 Most often, scope and center comes from user's input:
 
@@ -256,30 +230,23 @@ But sometimes, this implementation does not fits the needs:
 
 For this reasons, associated center and scopes must be resolved programmatically. The default implementation rely on the model association, as described above. But it becomes possible to change the behaviour on different implementations.
 
-Is my entity "concerned" by scopes ?
-------------------------------------
+### Is my entity "concerned" by scopes ?
 
 Some entities are concerned by scope, some not.
 
 This is also programmatically resolved.
 
-The concepts translated into code
-===================================
+## The concepts translated into code
 
-.. figure:: /_static/access_control_model.png
    
    Schema of the access control model
 
 Chill handle **entities**, like *persons*, *reports* (associated to *persons*), *activities* (also associated to *_persons*), ... On creation, those entities are linked to one center and, eventually, to one scope. They implements the interface `HasCenterInterface`.
 
-.. note::
-
    Somes entities are linked to a center through the entity they are associated with. For instance, *activities* or *reports* are associated to a *person*, and the person is associated to a *center*. The *report*'s *center* is always the *person*'s *center*.
 
 Entities may be associated with a scope. In this case, they implement the `HasScopeInterface`.
 
-.. note::
-
    Currently, only the *person* entity is not associated with a scope. 
 
 At each step of his lifetime (creation, view of the entity and eventually of his details, update and, eventually, deletion), the right of the user are checked. To decide wether the user is granted right to execute the action, the software must decide with those elements :
@@ -291,13 +258,10 @@ At each step of his lifetime (creation, view of the entity and eventually of his
 
 All those action are executed through symfony voters and helpers. 
 
-How to check authorization ?
-============================
+## How to check authorization ?
 
 Just use the symfony way-of-doing, but do not forget to associate the entity you want to check access. For instance, in controller :  
 
-.. code-block:: php
-
    class MyController extends Controller 
    {
 
@@ -311,12 +275,9 @@ Just use the symfony way-of-doing, but do not forget to associate the entity you
 
 And in template :
 
-.. code-block:: twig
-
    {{ if is_granted('CHILL_ENTITY_SEE', entity) %}print something{% endif %}
 
-Retrieving reachable scopes and centers for a user
---------------------------------------------------
+### Retrieving reachable scopes and centers for a user
 
 The class :class:`Chill\\MainBundle\\Security\\Authorization\\AuthorizationHelperInterface` helps you to get centers and scope reachable by a user.
 
@@ -325,9 +286,7 @@ Those methods are intentionnaly build to give information about user rights:
 - getReachableCenters: to get reachable centers for a user
 - getReachableScopes : to get reachable scopes for a user
 
-
-Adding your own roles
----------------------
+### Adding your own roles
 
 Extending Chill will requires you to define your own roles and rules for your entities. You will have to define your own voter to do so.
 
@@ -336,28 +295,20 @@ To create your own roles, you should:
 * implement your own voter. This voter will have to extends the :class:`Chill\\MainBundle\\Security\\AbstractChillVoter`. As defined by Symfony, this voter must be declared as a service and tagged with `security.voter`;
 * declare the role through implementing a service tagged with `chill.role` and implementing :class:`Chill\\MainBundle\\Security\\ProvideRoleInterface`.
 
-.. note::
-
    Both operation may be done through a simple class: you can implements :class:`Chill\\MainBundle\\Security\\ProvideRoleInterface` and :class:`Chill\\MainBundle\\Security\\AbstractChillVoter` on the same class. See live example: :class:`Chill\\ActivityBundle\\Security\\Authorization\\ActivityVoter`, and similar examples in the `PersonBundle` and `ReportBundle`.
 
-.. seealso::
-
-   `How to Use Voters to Check User Permissions <http://symfony.com/doc/current/cookbook/security/voters_data_permission.html>`_
+   `How to Use Voters to Check User Permissions ](http://symfony.com/doc/current/cookbook/security/voters_data_permission.html)
 
    From the symfony cookbook
 
-   `New in Symfony 2.6: Simpler Security Voters <http://symfony.com/blog/new-in-symfony-2-6-simpler-security-voters>`_
+   [New in Symfony 2.6: Simpler Security Voters ](http://symfony.com/blog/new-in-symfony-2-6-simpler-security-voters)
 
    From the symfony blog
 
-
-Declare your role
-^^^^^^^^^^^^^^^^^^
+##### Declare your role
 
 To declare new role, implement the class :class:`Chill\\MainBundle\\Security\\ProvideRoleInterface`. 
 
-.. code-block:: php
-
    interface ProvideRoleInterface
    {
        /**
@@ -375,21 +326,15 @@ To declare new role, implement the class :class:`Chill\\MainBundle\\Security\\Pr
        public function getRolesWithoutScope();
    }
 
-
 Then declare your service with a tag `chill.role`. Example : 
 
-.. code-block:: yaml
-
        your_service:
            class: Chill\YourBundle\Security\Authorization\YourVoter
            tags:
                - { name: chill.role }
 
-
 Example of an implementation of :class:`Chill\\MainBundle\\Security\\ProvideRoleInterface`:
 
-.. code-block:: php
-
    namespace Chill\PersonBundle\Security\Authorization;
 
    use Chill\MainBundle\Security\ProvideRoleInterface;
@@ -412,13 +357,10 @@ Example of an implementation of :class:`Chill\\MainBundle\\Security\\ProvideRole
 
    }
 
-Adding role hierarchy
-^^^^^^^^^^^^^^^^^^^^^
+##### Adding role hierarchy
 
 You should prepend Symfony's security component directly from your code. 
 
-.. code-block:: php
-
    namespace Chill\ReportBundle\DependencyInjection;
    use Symfony\Component\DependencyInjection\ContainerBuilder;
    use Symfony\Component\Config\FileLocator;
@@ -450,10 +392,7 @@ You should prepend Symfony's security component directly from your code.
        }
    }
 
-
-
-Implement your voter
-^^^^^^^^^^^^^^^^^^^^
+##### Implement your voter
 
 Most of the time, Voter will check that:
 
@@ -464,7 +403,6 @@ Most of the time, Voter will check that:
 
 Thats what we call the "autorization logic". But this logic may be replace by a new one, and developers should take care of it.
 
-
 Then voter implementation should take care of:
 
 * check the access to associated entities. For instance, if an ``Activity`` is associated to a ``Person``, the voter should first check that the user can show the associated ``Person``;
@@ -472,9 +410,6 @@ Then voter implementation should take care of:
 
 This is an example of implementation:
 
-
-.. code-block:: php
-
    <?php
 
    namespace Chill\DocStoreBundle\Security\Authorization;
@@ -513,7 +448,6 @@ This is an example of implementation:
                ->build();
        }
 
-
        protected function supports($attribute, $subject)
        {
            return $this->voterHelper->supports($attribute, $subject);
@@ -553,7 +487,6 @@ This is an example of implementation:
            // ...
        }
 
-
        public function getRolesWithHierarchy()
        {
            // ...
@@ -562,8 +495,6 @@ This is an example of implementation:
 
 Then, you will have to declare the service and tag it as a voter :
 
-.. code-block:: yaml
-
    services:
        chill.report.security.authorization.report_voter:
            class: Chill\ReportBundle\Security\Authorization\ReportVoter
@@ -572,18 +503,13 @@ Then, you will have to declare the service and tag it as a voter :
            tags:
             - { name: security.voter }
 
-
-How to resolve scope and center programmatically ?
-==================================================
+## How to resolve scope and center programmatically ?
 
 In a service, resolve the center and scope of an entity
 
-.. code-block:: php
-
    use Chill\MainBundle\Security\Resolver\CenterResolverDispatcher;
    use Chill\MainBundle\Security\Resolver\ScopeResolverDispatcher;
 
-
    class MyService {
       private ScopeResolverDispatcher $scopeResolverDispatcher;
       private CenterResolverDispatcher $centerResolverDispatcher;
@@ -605,8 +531,6 @@ In a service, resolve the center and scope of an entity
 
 In twig template, resolve the center:
 
-.. code-block:: twig
-
    {# resolve a center #}
 
    {% if person|chill_resolve_center is not null%}
@@ -628,8 +552,6 @@ In twig template, resolve the center:
 
 In twig template, resolve the scope:
 
-.. code-block:: twig
-
    {% if entity|chill_is_scope_concerned %}
 
       {% if entity|chill_resolve_scope is iterable %}
@@ -645,8 +567,7 @@ In twig template, resolve the scope:
       {% endfor %}
    {%- endif -%}
 
-What is the default implementation of Scope and Center resolver ?
------------------------------------------------------------------
+### What is the default implementation of Scope and Center resolver ?
 
 By default, the implementation rely on association into entities.
 
@@ -657,16 +578,14 @@ By default, the implementation rely on association into entities.
 
 Then, the default implementation will resolve the center and scope based on the implementation in your model.
 
-How to change the default behaviour ?
--------------------------------------
+### How to change the default behaviour ?
 
 Implements those interface into services:
 
 * ``Chill\MainBundle\Security\Resolver\CenterResolverInterface``;
 * ``Chill\MainBundle\Security\Resolver\ScopeResolverInterface``;
 
-Authorization into lists and index pages
-========================================
+## Authorization into lists and index pages
 
 Due to the fact that authorization model may be overriden, "list" and "index" pages should not rely on center and scope from controller. This must be delegated to dedicated service, which will be aware of the authorization model. We call them ``ACLAwareRepository``. This service must implements an interface, in order to allow to change the implementation.
 
@@ -674,14 +593,11 @@ The controller **must not** performs any DQL or SQL query.
 
 Example in a controller:
 
-.. code-block:: php
-
    namespace Chill\TaskBundle\Controller;
 
    use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
    use Chill\TaskBundle\Repository\SingleTaskAclAwareRepositoryInterface;
 
-
    final class SingleTaskController extends AbstractController
    {
 
@@ -729,11 +645,9 @@ Example in a controller:
        }
    }
 
-Writing ``ACLAwareRepository``
-------------------------------
+### Writing ``ACLAwareRepository``
 
-The ACLAwareRepository should rely on interfaces
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+##### The ACLAwareRepository should rely on interfaces
 
 As described above, the ACLAwareRepository will perform the query for listing entities, and take care of authorization.
 
@@ -743,9 +657,6 @@ The service must rely on this interface, and not on the default implementation.
 
 Example: at first, we design an interface for listing ``SingleTask`` entities: 
 
-
-.. code-block:: php
-
    <?php
 
    namespace Chill\TaskBundle\Repository;
@@ -782,8 +693,6 @@ Example: at first, we design an interface for listing ``SingleTask`` entities:
 
 Implements this interface and register the interface as an alias for the implementation.
 
-.. code-block:: yaml
-
    services:
        Chill\TaskBundle\Repository\SingleTaskAclAwareRepository:
            autowire: true
@@ -791,8 +700,7 @@ Implements this interface and register the interface as an alias for the impleme
 
        Chill\TaskBundle\Repository\SingleTaskAclAwareRepositoryInterface: '@Chill\TaskBundle\Repository\SingleTaskAclAwareRepository'
 
-Write the basic implementation for re-use: separate authorization logic and search logic
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+##### Write the basic implementation for re-use: separate authorization logic and search logic
 
 The logic of such repository may be separated into two logic:
 
@@ -803,8 +711,6 @@ This logic should be separated into your implementation.
 
 Considering this simple interface:
 
-.. code-block:: php
-
    interface MyEntityACLAwareRepositoryInterface {
 
        public function countByAuthorized(array $criterias): int;
@@ -815,15 +721,11 @@ Considering this simple interface:
 
 The base implementation should separate the logic to allow an easy reuse. Here, the method ``buildQuery`` build a basic query without authorization logic, which can be re-used. The authorization logic is dedicated to a private method. For ease of user, the logic of adding ordering criterias and pagination parameters (``$start`` and ``$limit``) are also delegated to a public method.
 
-
-.. code-block:: php
-
    namespace Chill\MyBundle\Repository;
 
    use Doctrine\ORM\EntityManagerInterface;
    use Doctrine\ORM\QueryBuilder;
 
-
    final class MyEntityACLAwareRepository implements MyEntityACLAwareRepositoryInterface {
 
        private EntityManagerInterface $em;
@@ -875,15 +777,12 @@ The base implementation should separate the logic to allow an easy reuse. Here,
 
 Once this logic is executed, it becomes easy to make a new implementation of the repository:
 
-.. code-block:: php
-
    namespace Chill\MyOtherBundle\Repository;
 
    use Doctrine\ORM\EntityManagerInterface;
    use Doctrine\ORM\QueryBuilder;
    use Chill\MyBundle\Repository\MyEntityACLAwareRepository
 
-
    final class AnotherEntityACLAwareRepository implements MyEntityACLAwareRepositoryInterface {
 
        private EntityManagerInterface $em;
@@ -921,14 +820,8 @@ Once this logic is executed, it becomes easy to make a new implementation of the
 
 Then, register this service and decorates the old one:
 
-.. code-block:: yaml
-
    services:
        Chill\MyOtherBundle\Repository\AnotherEntityACLAwareRepository:
            autowire: true
            autoconfigure: true
-           decorates: Chill\MyBundle\Repository\MyEntityACLAwareRepositoryInterface:
-
-
-
-
+           decorates: Chill\MyBundle\Repository\MyEntityACLAwareRepositoryInterface: