mirror of https://github.com/usememos/memos
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
When using the dedicated feature in Memos' user settings to export all memos to Markdown files inside a ZIP folder, the output doesn't feature any kind of distinction for memos by their set visibility. While this is not a big issue for personal backups, it can reveal itself problematic if exporting the data to share it with other people, or maybe deploy to a static site generator, because there is nothing in the files that distinguishes public memos from private or workspace-restricted ones. This pull request simply modifies the ExportMemos server function, to add the Visibility status to the end of every exported file name inside the ZIP, right after the date (which is left intact). For example, the file for a public memo would now be called: `YYYY-MM-DDThh:mm:ss+hh:mm-PUBLIC.md`. An alternative solution would have been to write this information in a YAML header at the beginning of every Markdown file, but, since those are not used anywhere else in the software, I decided to stick with what is already used for export metadata, the filename. |
1 year ago | |
|---|---|---|
| .. | ||
| acl.go | 2 years ago | |
| acl_config.go | 2 years ago | |
| activity_service.go | ||
| auth.go | ||
| auth_service.go | 2 years ago | |
| common.go | 2 years ago | |
| idp_service.go | 2 years ago | |
| inbox_service.go | 2 years ago | |
| logger_interceptor.go | ||
| markdown_service.go | 1 year ago | |
| memo_relation_service.go | ||
| memo_resource_service.go | 2 years ago | |
| memo_service.go | 1 year ago | |
| reaction_service.go | 2 years ago | |
| resource_name.go | ||
| resource_service.go | 2 years ago | |
| user_service.go | 2 years ago | |
| v1.go | 2 years ago | |
| webhook_service.go | 1 year ago | |
| workspace_service.go | 1 year ago | |
| workspace_setting_service.go | 1 year ago | |