You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README talks about the "relative ease" with which custom reports can be created, but in my experience attempting to follow the recommendation to create a custom add-on for a simple report change is difficult/requires significant plone knowledge/overkill.
What If there were a custom report directory specified and created (empty) by default as part of this module, which I could then mount as a volume in my docker configuration and add my own reports to that exposed folder without affecting/applying any other source code modifications/addon creation.
Module upgrades would not be impacted by my additions.
It would greatly simplify my ability to add custom reports in a manageable/supportable way!
Thanks for your consideration
The text was updated successfully, but these errors were encountered:
Continuing on from this forum thread:
https://community.senaite.org/t/where-to-find-senaite-impress-default-pt/600/10
The README talks about the "relative ease" with which custom reports can be created, but in my experience attempting to follow the recommendation to create a custom add-on for a simple report change is difficult/requires significant plone knowledge/overkill.
What If there were a custom report directory specified and created (empty) by default as part of this module, which I could then mount as a volume in my docker configuration and add my own reports to that exposed folder without affecting/applying any other source code modifications/addon creation.
Module upgrades would not be impacted by my additions.
It would greatly simplify my ability to add custom reports in a manageable/supportable way!
Thanks for your consideration
The text was updated successfully, but these errors were encountered: