-
-
Notifications
You must be signed in to change notification settings - Fork 824
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
Add MessageTemplate api to v4 #17073
Conversation
(Standard links)
|
@eileenmcnaughton i think that needs to be a subdirectory up i.e. in Civi/Api4 |
762ee6b
to
6f12d1f
Compare
opps you are right! |
Civi/Api4/MsgTemplate.php
Outdated
* | ||
* @package CRM | ||
* @copyright CiviCRM LLC https://civicrm.org/licensing | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RIP $Id$
we miss you.
test this please |
6f12d1f
to
7189389
Compare
7189389
to
483f05a
Compare
I'm looking to cleanup this form to use the apiv4 (I'd rather got the extra step & switch it to an afform but that seems like too big a leap). This switches the loading to use apiv4. Note that 1) I decided that it doesn't make sense to setCheckPermissions = FALSE - I think the form should not be availble to non-permissioned users (& perhaps a hook might like to play a role here). 2) I removed the inheritence from the parent which seemed to do 3 things - added admin.css - none of the classes seemed to apply - added iconpicker - didn't seem to apply - loaded the defaults - which this change does on the form more succinctly
be0759b
to
33b33ab
Compare
@colemanw can you recheck this - I altered the form to use apiv4 as well & added some notes to the PR template & I'd like your feedback as apiv4 calls in core are fairly new In the process of this I would note that I could also have used apiv3 & I can now see that the EntityFormTrait would have worked too (FYI ) but I was kind of trying to get familiar with increasing v4 usage in core @mattwire we should possibly switch the EntityFormTrait to use apiv4. I think we could just switch
to
But we'd need some noisy fallback to apiv3 where there isn't a v4 entity |
Yes it all still looks good. |
Overview
Basic add of MessageTemplate entity to apiv4 & use if from core form
Before
Not there
After
Ta-da
Technical Details
I'm looking to cleanup this form to use the apiv4 (I'd rather got the extra step & switch it to an afform but
that seems like too big a leap).
This switches the loading to use apiv4. Note that
I decided that it doesn't make sense to setCheckPermissions = FALSE - I think the form should not
be availble to non-permissioned users (& perhaps a hook might like to play a role here).
I removed the inheritence from the parent which seemed to do 3 things
Comments