vivid: should not need to hard code child scopes in settings
Bug #1454391 reported by
Kyle Nitzsche
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| scope-aggregator |
Fix Released
|
High
|
Kyle Nitzsche | ||
Bug Description
starting with vivid, settings are auto added for all scopes returned by find_child_
currently, we may have dup settings for those added to settings.ini and found as keyword scopes (for which settings are auto added).
| Changed in scope-aggregator: | |
| assignee: | nobody → Kyle Nitzsche (knitzsche) |
Revision history for this message
| Kyle Nitzsche (knitzsche) wrote | #1 |
| Changed in scope-aggregator: | |
| status: | New → Fix Released |
To post a comment you must log in.
This was fixed a while ago with the completed support for keyword child scope aggregation implemented.