Folder exports broken, slashes are getting replaced with hyphens when exporting

[5310]

trafficstars

• App version: 0.7.3-3
• The output of screenfetch:

 » screenfetch 

 ██████████████████  ████████     scio@unum
 ██████████████████  ████████     OS: Manjaro 21.0.4 Ornara
 ██████████████████  ████████     Kernel: x86_64 Linux 5.10.34-1-MANJARO
 ██████████████████  ████████     Uptime: 2h 41m
 ████████            ████████     Packages: 1358
 ████████  ████████  ████████     Shell: bash 5.1.4
 ████████  ████████  ████████     Resolution: 1920x1080
 ████████  ████████  ████████     DE: KDE 5.81.0 / Plasma 5.21.4
 ████████  ████████  ████████     WM: KWin
 ████████  ████████  ████████     GTK Theme: Materia-dark [GTK2/3]
 ████████  ████████  ████████     Icon Theme: Papirus-Dark
 ████████  ████████  ████████     Disk: 893G / 1.1T (91%)
 ████████  ████████  ████████     CPU: Intel Core i5 750 @ 4x 2.667GHz
 ████████  ████████  ████████     GPU: GeForce GTX 650
                                  RAM: 6504MiB / 7949MiB

• Type of installed package (Snap, AppImage, deb, rpm, pacman): AUR

Bug description Exporting a frame or object with a / in its name should create a folder structure treating the name as a path. Instead, it converts the /es to -s.

This is a recent change (a couple of weeks or so). Before this standard Figma feature has always worked from within figma-linux.

This feature also still works on the web.

This change also seems to affect the overwrite check triggered when exporting some file that already exists through figma-linux. In this dialog it still retains the /, but under the hood it actually checks the hyphenated version of the flat filename and notifies the user if it already exists.

Screenshots In this demo file created to test this issue there is only one frame called a/b/c.

The export button even shows the export target as c.png:

When exported it outputs a-b-c.png in the export directory:

When trying to export while a-b-c.png still exists, it raises the overwrite alert as such:

It works fine when exported from the web, packaged inside a zip archive.

[5310]

Just for the record (not to hurry you or anything :), the bug persists in version 0.7.4-1 that I just updated to this morning.