[MAGNOLIA-1491] filters: remove priority, allow sub chains Created: 27/Apr/07  Updated: 23/Jan/13  Resolved: 02/May/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 3.1 M2

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Priority:
Since the current FilterManager reads the filters only from one single place (server/filters) we should use the order instead the priority. Otherwise the FilterManager should become a normal ObservedManager, where all modules register there filter.

Subchains:

  • it can be very anoying to copy alle the bypass definitions (since they are similar for most of the filters). We could simply allow a hierarchy of chains by making the main filter a magnolia filter itself. You could use this filter to configure subchains


 Comments   
Comment by Philipp Bracher [ 02/May/07 ]

done

Generated at Mon Feb 12 03:27:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.