[MAGNOLIA-7633] JCR browser asset export creates bootstrapfiles with too many dots Created: 13/Sep/19 Updated: 19/Sep/19 Resolved: 19/Sep/19 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.2 |
| Fix Version/s: | 6.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Rishab Dhar |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0.95h | ||
| Time Spent: | 31m | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
Given you have these assets, where the asset name contains a dot:
When exporting assets separately with the JCR browser.
|
| Comments |
| Comment by Rishab Dhar [ 19/Sep/19 ] |
|
The reason that supernumerous dot separating the filename from its extension would be a bug is based on the assumption that it would prevent reimport of the asset exported in that format. However, it has been tested that such an asset with supernumerous dot can be successfully reimported. Under the assumption that the supernumerous dot prevents reimport, the solution treats last fragment of the asset name specially by excluding it from createExportPath pre processing step (as the set of filenames is quite large and constantly evolves, it is hard to make assumptions on whether the fragment following the dot in an asset name is a file extension or not). |