- Issue created by @goodboy
- First commit to issue fork.
- Status changed to Needs review
over 1 year ago 6:23pm 8 August 2023 - last update
over 1 year ago 2 pass - 🇺🇸United States mrweiner
For some reason I'm having trouble pushing to the issue fork, but here's a patch to make base fields work. The module has a preg_match in it's logic to only allow "field_" fields. The patch just removes this and then adds a nullable check for target_bundles, since it may not be present on a base field at all.
- last update
over 1 year ago 2 pass - @mrweiner opened merge request.
- 🇺🇸United States mrweiner
Sorry for the mess of branches and patches. The MR should be the correct updates and the correct fork/branch. The MR also includes asort() on the options, which isn't present in the patch. Not sure whether this needs tests or not. Maybe a module setting for whether to include base fields?
- 🇺🇸United States mrweiner
This actually may duplicate the discussion in https://www.drupal.org/project/cer/issues/2998138 ✨ Could support Remove field name prefix module? Needs work
- 🇺🇦Ukraine goodboy Kharkiv, Ukraine
Thanks, @mrweiner
I've created a light custom module which used the CER Resolver. I don't use entities and store an entity referenced map to YML-file.
As I understand it, it makes no sense to publish my module as a separate ones.