[MAGNOLIA-6908] YAML includes should't be placed inside of dialogs/templates folder Created: 22/Dec/16 Updated: 08/Jun/20 Resolved: 08/Jun/20 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | resource-loader |
| Affects Version/s: | 5.4.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Workaround exists | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
If you place an YAML include file into the dialogs/templates folders, it's loaded into the registry which is not support to be in and might produce false positive errors visible the definitions app. We should: |
| Comments |
| Comment by Roman Kovařík [ 22/Dec/16 ] |
|
[11:38 AM] Mikaël Geljić: right, @Roman this is how I typically had yaml includes, so that they don't mess with registries |
| Comment by Richard Gange [ 09/Aug/18 ] |
|
If you use .yml instead of .yaml this also works. Dot yml files are treated as plain resources instead of definition resources. However, both are valid yaml extensions so syntax highlighting remain in most editors. |
| Comment by Richard Gange [ 08/Jun/20 ] |
|
The workaround is to put the includes directory outside the registry. |