Hope to add an option of "Save to SiYuan" in the integration module.
Clear and concise description of the problem
我看到集成中添加了保存到obsidian的选项,所以就像提提关于导出到思源的功能
Suggested solution
https://github.com/siyuan-note/siyuan 这里是思源笔记的开源地址
Alternative
No response
Additional context
No response
Validations
- [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
我看导出到ob是有pr的,不是follow开发者做的,所以就关闭issue了
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
I see that there is a PR when exporting to ob, and it is not done by follow developers, so I closed the issue
Bot 检测到 issue body 的语言不是英文,自动翻译。👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
我看到导出到 ob 时有一个 PR,而且不是由跟随开发人员完成的,所以我关闭了这个问题
群友似乎要出手pr,所以重新打开issue
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Bot detects that the language of the issue body is not English and automatically translates it. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
I saw there was a PR when exporting to ob, and it wasn't done by a follow developer, so I closed the issue
It seems that the group friends are going to PR, so I reopen the issue
Is it similar to obsidian support? Is exporting the markdown file to a specific folder enough?
Is it similar to obsidian support? Is exporting the markdown file to a specific folder enough?
It is supported api to import md file, all the api route are in the file router.go. I’m using cell phone can not give you the link now.
Is it similar to obsidian support? Is exporting the markdown file to a specific folder enough?
There are APIs for uploading resource files and Markdown text content.
ok, if anyone wants to help support it, just send a PR
I have same requirement.
Please change "Siyuan" in the title to "SiYuan". I am in the late stage of obsessive-compulsive disorder.
Thank you for your suggestion.
麻烦把标题中的 "Siyuan" 改为 "SiYuan",我是强迫症晚期。
谢谢你的提议。
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Follow or in the beta—please include it with your comment!
bump
我试了一下最新的自定义集成,会报错 400:
去掉 [content_markdown] 就能正常保存:
@Innei 日志基本是这样:
[2025-08-14 21:05:34.401] [info] (main) [CustomFetch:wevolr] Starting request {
url: 'http://127.0.0.1:6806/api/filetree/createDocWithMd',
method: 'POST',
timeout: 30000,
hasBody: true,
bodyLength: 428,
headerCount: 2
}
[2025-08-14 21:05:34.402] [debug] (main) [CustomFetch:wevolr] Request headers {
headers: { Authorization: '***', 'Content-Type': 'application/json' }
}
[2025-08-14 21:05:34.402] [debug] (main) [CustomFetch:wevolr] Request body {
body: '{\n' +
' "notebook": "20250807223039-xglr4at",\n' +
' "tags": "!剪藏",\n' +
' "path": "/英伟达宣布了结束旧架构 GPU 驱动支持的时间表",\n' +
' "markdown": "英伟达宣布,自 2025 年 10 月起新 Game Ready 驱动更新将不再支持 Maxwell、Pascal 或 Volta GPU 架构。这意味着 GeForce GTX 1060 之类的旧显卡将不再获得针对新游戏进行优化的驱动版本。英伟达还表示将于 2026 年 10 月停止所有 Windows 10 驱动支持,比微软官方的 Windows 10 终止支持时间晚一年。此后如果 Windows 10 用户希望继续获得较新型号显卡的新驱动,他们需要升级到 Windows 11。英伟达表示会在 2028 年 10 月之前为 Maxwell、Pascal 和 Volta 系列显卡发布季度安全更新。\n' +
'"\n' +
'}'
}
[2025-08-14 21:05:34.403] [debug] (main) [CustomFetch:wevolr] Sending request...
[2025-08-14 21:05:34.405] [info] (main) [CustomFetch:wevolr] Request completed { status: 400, statusText: 'Bad Request', ok: false, duration: '2ms' }
[2025-08-14 21:05:34.406] [debug] (main) [CustomFetch:wevolr] Response headers {
headers: {
'access-control-allow-credentials': 'true',
'access-control-allow-headers': 'origin, Content-Length, Content-Type, Authorization',
'access-control-allow-methods': 'GET, HEAD, POST, PUT, PATCH, DELETE, CONNECT, OPTIONS, TRACE',
'access-control-allow-origin': '*',
'access-control-allow-private-network': 'true',
'content-encoding': 'gzip',
'content-length': '77',
date: 'Thu, 14 Aug 2025 13:05:34 GMT',
vary: 'Accept-Encoding'
},
contentLength: '77'
}
[2025-08-14 21:05:34.408] [debug] (main) [CustomFetch:wevolr] Response body received {
size: '53 chars',
preview: '{"code":-1,"msg":"parses request failed","data":null}'
}
[2025-08-14 21:05:34.408] [debug] (main) [CustomFetch:wevolr] Response successfully parsed as JSON
[2025-08-14 21:05:34.408] [info] (main) [CustomFetch:wevolr] Request successful {
finalStatus: 'http_error',
responseSize: '53 chars',
totalDuration: '5ms'
}
可能是字符转义的问题 我修一下
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Maybe it's a character escape problem. I'll fix
看上去是 思源笔记的问题 没有详细的响应错误信息。无法排查
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
It looks like a problem with Siyuan Notes. There is no detailed response error message. Cannot check
400 错误,http 请求 ~~没有发送到思源内核~~ 参数格式错误导致被直接忽略了,根本没有处理。~~Folo 怎么调试我也不知道~~ 找到贡献文档了:https://github.com/RSSNext/Folo?tab=contributing-ov-file#readme
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
400 Error, http request was not sent to Siyuan kernel. I don't know how to debug Folo
@Innei 我在思源里加日志调试了一下,请求 JSON 里出现了意外的换行符
I also hope to have the feature of saving to SiYuan Notes. Thank you very much to developer for their hard work.
@lawvs 还是有个多余的换行符,麻烦再看看。
我在 Folo 里配置的请求体:
{
"notebook": "20250807223039-xglr4at",
"tags": "!剪藏",
"path": "/[title]",
"markdown": "[content_markdown]"
}
请求时会在 [content_markdown] 之后有一个多余的换行符:
@TCOTC 为了兼容其他未知的格式,开启转义需要添加一个 Content-Type: application/json 的请求头,可以加上试试
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
@TCOTC In order to be compatible with other unknown formats, you need to add a Content-Type: application/json request header to enable escaping. You can add it and try
@lawvs
生产环境还没有发布,需要稍等,我测试了你的配置,可以正常转义
意思是 Desktop v1.1.7 和 v1.2.0 都还没有吗?
话说我刚刚装了最新的 v1.1.7 发现没法 Ctrl+Shift+I 按出开发者工具了
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Does it mean that Desktop v1.1.7 and v1.2.0 are not available yet?