| Comment | File | Size | Author |
|---|---|---|---|
| #14 | deprecated_method_entity_manager-3083331-14-interdiff.txt | 4.06 KB | berdir |
| #14 | deprecated_method_entity_manager-3083331-14.patch | 10.78 KB | berdir |
| #10 | deprecated_method_entity_manager-3083331.patch | 10.7 KB | pratik_kamble |
| #2 | 3083331-2.patch | 899 bytes | ravi.shankar |
Comments
Comment #2
ravi.shankar commentedI have removed.
Comment #3
pratik_kamblePatch LGTM.
Comment #4
berdirThere are a lot more remaining entity.manager usages:
Comment #5
pratik_kambleComment #6
pratik_kambleStarting work on it.
Comment #7
ravi.shankar commentedOk @pratik_kamble
Comment #8
berdir@pratik_kamble, are you still working on this? If you're stuck then I'd suggest you post what you have and unassign, so that someone else can pick it up.
Comment #9
pratik_kamble@Berdir yes I am still working. I will post the patch by tomorrow.
Comment #10
pratik_kamblePlease find the attached patch to remove the use of the EntityManagerInterface.
Comment #11
ravi.shankar commentedThe above patch has failed in some tests so back to needs work.
Comment #12
berdirYou need to check what service the parent needs.
Alternatively, we could use the new pattern that doesn't require a constructor, see https://www.previousnext.com.au/blog/safely-extending-drupal-8-plugin-cl...
we can remove the constructor here completely because the parent now has entityTYpeBundleInfo.
Comment #13
berdirI'll have a look at this, this has some tricky parts.
Comment #14
berdirLets see about this.
Comment #16
berdirCommitted.