Further generalization as conditions API for routes?

Created on 5 April 2023, over 1 year ago

Problem/Motivation

Just came across your interesting module and that made me think, it we could add a further API layer below the entity level here to make it even usable for other modules, which are not based on entities.

I already saw several modules implementing the conditions logic used here, which we know similarly from blocks or "Context" module in modules like

  • Google Analytics
  • GA
  • Facebook
  • Libraries like Photoswipe, Choices, ...
  • And many other I don't remember right now

All off them are currently reinventing the wheel...
Wherever conditions come in, typically by path, to decide if something should be loaded / shown on the given path.

Best would be to have the lower level API in core, but this module could be a super nice starting point, perhaps separating the entity based logic into a submodule then?

What do you think about this?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany Anybody Porta Westfalica

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024