[CONTEDIT-161] Offer better flexibility in linking stories than hardcoding parent folders like our demo does Created: 19/Oct/17 Updated: 16/Jun/21 Resolved: 16/Jun/21 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Zdenek Skodik | Assignee: | Unassigned |
| Resolution: | Outdated | 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)
|
||||
| Date of First Response: | |||||
| Description |
|
On one hand stories can be stored at rather complex hierarchies of folders and moved/restructured anytime the input conditions have changed. On the other stories are referenced by URL selectors by name, its ancestors supplied arbitrary for the RepositoryMappings to resolve requested story correctly. This is not much in line with the user experience the app offers and is potentially pretty error prone ending up in not delivering content that exists. Travel demo hard codes parent folder in the script (/travel-demo-stories-app/templates/shared/functions.ftl), sticking the story on its current place, preventing them to be further structured into subfolder or even moved out of it. This is due to RepositoryMappingFilter#74. |