Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Specify the config export download filename in the modern way #3243

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

jswalden
Copy link
Contributor

@jswalden jswalden commented Feb 3, 2025

Fixes #3242. I got bogged down where I was, so I was able to test this in Safari (as well as the more cross-platform Firefox and Chrome).

I believe this is a bugfix that could reasonably be taken in a point release (although I developed it against main and haven't checked whether it would backport). I actually ran into this trying to avail myself of this using the current .companionconfig naming style I have for my own site backups when I make changes (in this case, after doing the s/internal:custom_/custom:/g change throughout my configuration), and it would be nice to be able to make use of this feature and not change my previous naming style to work around this.

…at's interpreted identically in all modern browsers. (bitfocus#3242)
@jswalden jswalden force-pushed the export-file-name-specialchars branch from 8a923e5 to c80b1b3 Compare February 3, 2025 06:16
@Julusian Julusian merged commit 6425196 into bitfocus:main Feb 3, 2025
4 of 5 checks passed
@Julusian Julusian added this to the v3.5 milestone Feb 3, 2025
@jswalden jswalden deleted the export-file-name-specialchars branch February 3, 2025 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

[BUG] Special characters in the export filename get URL-encoded in Safari
2 participants