[MGNLUI-5369] Updated JcrExportAction constructs wrong file name Created: 12/Sep/19  Updated: 24/Sep/19  Resolved: 19/Sep/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.1.2
Fix Version/s: 6.2

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Rishab Dhar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 5h
Time Spent: 4.25h
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
Epic Link: UI framework: basic features
Sprint: UI Framework 6

 Description   

The former implementation would use DataTransporter.decodePath(getCommand().getFileName(), DataTransporter.UTF8) whereas the JcrExportAction would merely use the asset name + extension.

as a result the exported bootstrap file doesn't include path at all.


Generated at Mon Feb 12 09:25:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.