1. We need to improve our provided module integration to not work with configuration if it doesn't make sense, i.e. disable the rules-integration.
2. We need to come up with a good way for us and for modules to determine entity types being configuration.
Proposal for 2)
- Use $entity_info['configuration'] = TRUE | FALSE
- By default, treat everything being exportable as configuration.
Questionable is how we should ease applying the default. We could provide a function like entity_type_is_configuration()
. Or simpler, we just apply the default in entity_entity_info_alter(), for which we already make sure (or better we try to make sure) it runs last. Not ideal, but it should do it.
Thoughts?
Comment | File | Size | Author |
---|---|---|---|
#2 | entity_configuration.patch | 1.37 KB | fago |
Comments
Comment #1
fagoadding tag
Comment #2
fagoImplemented variant 2) - feedback wanted.
Comment #3
bojanz CreditAttribution: bojanz commentedLooks good to me.
Had a similar thought a few weeks back, definitely useful.
Comment #4
fagook, committed. :)