Skip to content

fix: add workaround for wrong config file extension on some browsers #638

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.

Sign up for GitHub

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

Merged
t-aleksander merged 3 commits into from
Jun 3, 2024
Merged

fix: add workaround for wrong config file extension on some browsers #638

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8f5ad35
fix file extension on some browsers
t-aleksander Jun 3, 2024
894e863
remove charset as its unsued according to the standard
t-aleksander Jun 3, 2024
319dd05
Merge branch 'dev' into fix-file-extension
t-aleksander Jun 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion web/src/shared/utils/downloadWGConfig.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@ import saveAs from 'file-saver';

export const downloadWGConfig = (config: string, fileName: string) => {
const blob = new Blob([config.replace(/^[^\S\r\n]+|[^\S\r\n]+$/gm, '')], {
type: 'text/plain;charset=utf-8',
// octet-stream is used here as a workaround: some browsers will append
// an additional .txt extension to the file name if the MIME type is text/plain.
type: 'application/octet-stream',
});
saveAs(blob, `${fileName.toLowerCase()}.conf`);
};