-
Notifications
You must be signed in to change notification settings - Fork 150
Closed
Labels
Area: VendorType: EnhancementNew feature or functionality changeNew feature or functionality changeType: Tech DebtUse this label for decisions that will intentionally require refactor in the future.Use this label for decisions that will intentionally require refactor in the future.
Milestone
Description
Currently we have vendored wagtail_flexible_forms by @BertrandBordage in order to provide support and integration within CodeRed CMS.
This is fine, however it is an ideal candidate to be split out into a separate pip package. This would be relatively trivial because it is already namespaced within coderedcms. The advantage here is that other wagtail sites could use it, and it could be an optional part of coderedcms.
While I wouldn't want to step on Bertrand's toes by taking over the project, we would have to fork and take over it in order to provide a pip package. Since a pip package was never created that would not technically be a problem.
If anyone has any input, please speak now!
Requirements:
- Create separate
wagtail_flexible_formsrepository (While I would normally want to provide a fork, the code would then not be searchable on github, etc., and the original does not seem to be maintained). - Create at a minimum basic unit tests, ideally 60-70% coverage to ensure there is no major breakage.
- Document the package extensively. Currently there is no documentation.
- Publish a pip package
- Remove the code in coderedcms, and integrate the new package.
Metadata
Metadata
Assignees
Labels
Area: VendorType: EnhancementNew feature or functionality changeNew feature or functionality changeType: Tech DebtUse this label for decisions that will intentionally require refactor in the future.Use this label for decisions that will intentionally require refactor in the future.