Code in the Context sub-namespace is generally re-usable context handling code of Rules. While we want to keep the code in the repository to ease maintenance, we should provide it as its own composer package.

Issues / tasks to reach that goal:
- Context related tests should move below the Context namespace? Although probably most tests are in-direct and use Rules
- a Git sub-tree split necessary
- Data processors are currently use the plugin manager, which is a service. But the component cannot provide services?
- Keeping the code in the repository probably means keeping the namespace of \Drupal\rules\Context
- #2677094: Execution state and execution metadata state classes belong to the Context component
- Integrity checking needs to become a general concept, independent of Rules as well. E.g., move it to \Drupal\rules\ConfigIntegrity ? That means it would be a simple composer package also.

Comments

fago created an issue. See original summary.

fago’s picture

fago
Primary language German
Location Vienna
commented
Issue summary: View changes
tr’s picture

tr commented
Assigned: Unassigned » fago
Category: Task » Feature request
Status: Active » Postponed

I'm not planning on doing this in Rules. I think this should be deferred to Rules 8.x-4.x if at all. It will be an API change so it has to be done in alpha or in a new 8.x-4.x version. But since it will be a big task to split all that off, I don't think it makes any sense at all to delay the beta release for this issue.

tr’s picture

tr commented
Status: Postponed » Closed (won't fix)