-
-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REF Convert forms to standard customData template #13412
Conversation
(Standard links)
|
96469f7
to
62e185a
Compare
Jenkins re test this please |
Code review looks good. User testing:
|
@mattwire - found this problem while testing Surveys and Petitions: To reproduce:
Result:
Result:
|
Merging as per @colemanw 's review and tag |
@agileware I'm pretty sure you hit a bug on custom data - maybe on event info & this is a follow up to a short term revert on that? Maybe you could do some testing of master in your scenario/s |
Overview
This converts ALL forms that are adding customData in a similar way to use the
CRM/common/customDataBlock.tpl
file which was added as part of the entityForm work last year.Before
Each form adds custom data to the form in a similar way but using a copy of the code.
After
Each form adds custom data in exactly the same way.
Technical Details
The eventual goal is to convert all of these forms to use the entityFormTrait but that requires a significant amount of work on each form and is likely to introduce bugs requiring significant testing.
The change here standardizes the addition of customData across those forms, adding standard "getters" where necessary which will help with the eventual conversion to entityform.
In all cases, we are removing a few lines of code from each form which will make future maintenance easier and we can be sure that certain variables are assigned to each of the templates.
Comments
@eileenmcnaughton @seamuslee001 @lcdservices @alifrumin I realise this is quite a big PR and I could split out some of the commits into separate PRs - but I didn't want to flood the PR queue... As each of the form changes are self-contained perhaps you could test a couple each, and if there are any that cause issues, I'll pull them out as separate PRs for further work?