[MAGNOLIA-8255] QueryTask warning might be more subtle Created: 15/Dec/21 Updated: 15/Dec/21 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Description |
Steps to reproduce
Expected resultsIf I know the content I want to update a content that shouldn't be updated in the same Magnolia version update, I should be able to use the QueryTask without a warning (at least on the installation screen). Actual resultsQueryTask produces a warning introduced by WorkaroundUse the QueryTask despite the warning. Development notesThe warning was quite useful at the time it was introduced as we had huge amount of updates, often depending on changes in the same session. Nowadays are the update tasks rare especially due to do config in YAML and often developing only using light modules. |