- 🇨🇦Canada liquidcms
I agree entirely that this would be much cleaner if fillpdf forms with field definitions were config entities.
- Status changed to Postponed
3 months ago 2:54pm 5 September 2024
I must admit that from the very beginning, I was baffled that in the Drupal 8 version, FillPdfForms are Content Entities rather than Config Entities:
There’s only a limited number of them, they aren’t user facing, while they need a couple of settings they don’t necessarily have to be fieldable, but what they have to be is exportable and it’d be nice if they were shippable together with the PDF template. A typical case of a Config Entity, I would say.
The current approach works, and both Content Entities and Config Entities may have their up- and downsides, but for the 8.x-5.x version, I think we should at least make it a conscious and well thought through decision to stick with FillPdfForms being Content Entities even though they seem to be the perfect use case of a Config Entity.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I agree entirely that this would be much cleaner if fillpdf forms with field definitions were config entities.