Details
-
Improvement
-
Resolution: Unresolved
-
High
-
1.7.8, 1.13.4, 2.5.1
-
None
Description
Features that require the config resolver may be loaded too early, and behave incorrectly.
This has caused several strange support issues.
Since that situations is very complex to debug, a solution should be found to detect it, and warn the developer about that as early as possible, for instance using an exception.
Attachments
Issue Links
- relates to
-
EZP-26065 [SF 2.8] Cache warmup sets and leaves wrong siteaccess
- Closed
-
EZP-30546 Cache service has wrong instance on command line
- Documentation Review done
-
EZP-29416 Siteaccess scope 'global' broken
- InputQ
-
EZP-28774 Symfony 4.x: Config Resolver dynamic settings requires runtime interaction with private services
- Specification
-
EZP-30547 As a Developer I'd like to be able to debug config resolver & services
- Documentation Review done
- testing discovered
-
EZP-30722 Siteaccess is loaded after commands are loaded on run, triggering unnecessary config resolver warnings
- Closed