- Issue created by @kristiaanvandeneynde
- π§πͺBelgium gorkagr
Hi!
Thanks a lot for the roadmap :)Maybe
Stop saving an entity when it gets added to a group
is linked to #3057483 (core) π [PP-2] Better describe how SynchronizableInterface should be used for content entities Needs work and/or #2872697 (group) β / #3478088 (group) π Group relationship saving/deletion resaves entities without using ::setSyncing() ActiveBest
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
Uh yeah, there's an issue for that one already I just had to find it :) Thanks
- heddn Nicaragua
I thought I saw that
Disallow automatic membership outside of form approach
already made it in. Can we confirm?
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
From Group:
/** * {@inheritdoc} */ public function postSave(EntityStorageInterface $storage, $update = TRUE) { parent::postSave($storage, $update); // If a new group is created and the group type is configured to grant group // creators a membership by default, add the creator as a member unless it // is being created using the wizard. // @todo Deprecate in 8.x-2.x in favor of a form-only approach. API-created // groups should not get this functionality because it may create // incomplete group memberships. $group_type = $this->getGroupType(); if ($update === FALSE && $group_type->creatorGetsMembership() && !$group_type->creatorMustCompleteMembership()) { $values = ['group_roles' => $group_type->getCreatorRoleIds()]; $this->addMember($this->getOwner(), $values); } }
- π§πͺBelgium gorkagr
I have opened https://www.drupal.org/project/group/issues/3494986 π Review DI in classes and their construct methods Needs work to check the DI in controllers there (and maybe the __construct methods) :)
Best
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
Added to the list, along with "Drop constructor documentation and use property promotion where possible"
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
Added a kickass idea for a new editorial workflow
- πΊπΈUnited States moshe weitzman Boston, MA
Great to see this Roadmap.
Some nice to have (if applicable):
- Use SDC
- Integrate a top level menu item into Navigation module (maybe this is done automatically)
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
Could look into SDC, is there an example of applying it to entities? I don't think I have anything else in my hook_theme. The permissions UI uses an inline template for some small things.
The top level menu thing we definitely need to look into for D11.
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
List is getting smaller :) Next one to tackle is probably the easy navigation entry and then "Disallow automatic membership outside of form approach". The brand-new creation UI I'm on the fence whether I want to add this now or at a later time. Still deciding...
- π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
Thinking of lifting the new editor flow where we use contexts into a minor release. Already getting rid of the wizard in the issue about not allowing automatic memberships outside of the form approach so that's one step in the right direction. Then 4.1 could contain more context provider support.