[MGNLCT-129] rootPath should be checked and auto-created if set Created: 16/Jul/19 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | 1.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Scot Rhodes | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| 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)
|
| Date of First Response: |
| Description |
|
When a contentType has datasource.autoCreate set to true, and a rootPath is defined that is not at the root of the provided workspace, the rootPath should be checked for existence, and created if not. The result of this not occurring is that the app will not provide any action bar items to create an item since there is a non-existent path in the workspace. Additionally, if a rootPath is declared, the app that uses this content type should automatically include the contentConnector, i.e. |
| Comments |
| Comment by Christopher Zimmermann [ 16/Jul/19 ] |
|
Looks like a good improvement. |