[MGNLRES-407] config.yaml not accessible when only resource Created: 29/Sep/23 Updated: 17/Oct/23 |
|
| Status: | Open |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | 3.0.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Chris Jennings | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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 |
| Comments |
| Comment by Roman Kovařík [ 03/Oct/23 ] |
|
Is this really about the resources app? The Resources app displays anything on the classpath or file system. It doesn't matter what the directory or file name is; it doesn't perform any processing. The Definitions app would miss the module since it doesn't contain any definitions, though. |
| Comment by Chris Jennings [ 17/Oct/23 ] |
|
I'm not sure if that is correct. I have installed these two modules into a demo project: The 'samples' module relies on the other to provide YAML files that are included so I can be sure both are present. However, on opening the Resources app I only see one of the two modules. I think it must be doing some processing. |