thisisalistairsaccount
commented
3 years ago The current challenge with this module (https://www.drupal.org/project/webform_views) is that it its currently in alpha.
While it's good that it has D9 forward compatibility, we'd be really keen to see it hit stable before we could consider introducing something like this into the distribution
** What value does this module/package add to GovCMS?
Provides ability to filter/list and otherwise expose webworm submissions to Drupal views module.
** Please provide a brief outline of what this module does.
See above. Allows users to filter their various submission (e.g. applications)
** Who does this module benefit: [X] end users [ ] content editors [X] site builders [ ] themers [ ] developers
** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
Custom PHP - possibly which heavy lifting. This module saves time for the developer so we don't have to code.
Else, only /admin/structure/webform/manage/WEBFORM_ID/results/submissions is only way to see results.
** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
Nil.
** What is the maintenance and support status of the module. Describe the issue queue activity.
Last commit 5 months ago. It is Drupal 9 compatible. Issue queue is active - last comment 1 day ago.
** What permissions are needed to utilise the module (and are any new permissions provided by the module)?
Seems no permission. existing permissions of submission entities would be respected.
** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
Only database data is related to views. (so in views config files - new filter etc.)
** Is the module designed to capture anonymous user data?
No.
** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
Should be fully cachable as per views caching.
** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
Assess if some issues in issue queue are a big issue - else ok should be fine.
** Additional information