Sylvain Jermini
Sylvain Jermini
For #469 to be completely functional , we will need to remove all references of repositories and only use the alfio.manager.** layer. Some refactoring/cleanup will be done.
In the work for #469 , we will need to remove all the direct call from controller -> repository. As part of this cleanup, we should: - move all code...
The table `additional_service_field_value` is no more used -> could be dropped. The table `dynamic_field_template` is a read only table that contains some templates for the dynamic fields. It contains also...
Currently the templates are saved in the resource_* tables, but, in theory, with some refactoring they coud be folded in the configuration_* . Benefit: less tables, more coherent api. Note:...
As title, we often need to add some data which is generally common in all events. Identified as such: - tax + tax policy - currency - T&C, privacy url...
Currently we only support recaptcha for catpcha purpose. https://www.hcaptcha.com/ is a interesting alternative.
The endpoint `/api/v2/public/events` (https://github.com/alfio-event/alf.io/blob/master/src/main/java/alfio/controller/api/v2/user/EventApiV2Controller.java#L98) should be able to filter by: - tag - organization - type (online, ...) - full text search (this one could open some issues), maybe not...
Currently we have the following profiles defined: - dev - integration-test - !dev - spring-boot - demo - openid - disable-jobs Check which can be removed. As far as I...
Currently in `email_message` we save the resulting output of the templates in: - `message` - `htmlMessage` - `attachments` As a possible improvement we could generate the various data on demand....
we could trace some statistics while preserving the privacy of the users: - referrers - how many completed reservations vs how many cancelled for conversion rate - .... A single...