Hi @sethyuan, thanks a lot for this plugin!

One way to approach #10 and solve another great use case is to persist the data locally in the assets folder as CSV.

This is very consistent with how logseq handles non-text datatypes

• drawings are persisted in the draws subfolder
• images are persisted in the assets subfolder
• pdfs are persisted in the assets subfolder

Additionally this also enables a lot of other benefits, which I'd be most excited about

• Data is not locked into the serialization format used by luckysheet
• Much easier to handle larger tables in a dedicated table file format than markdown
• Edit data in a dedicated spreadsheet software, view in logseq
• Use tables as databases and reuse them across applications - e.g. do data engineering in a jupyter notebook, then read/view/comment in logseq
• use command-line utilities for quick data engineering - xsv, visidata, cut, ....

One option to implement:

Save button persists to disk in asset folder, vs storing in markdown This could be configurable in the plugin settings

First of all, I love this plugin!

Even through <br /> is correct markdown, it shows as is in a logseq block after exporting luckysheet to markdown.

This only happens if the table heading has <br /> but works ok if the a normal table row has it.

Instead, if I use [:br], it works fine and a new line is correctly rendered as the heading row in the logseq table block

Thank you!

Is there no way for the plugin to save the worksheet data in the logseq graph folder? I see that it saves it in $HOME/.logseq/storages/ but since that is not synced across all machines (and probably won't be synced by Logseq's new sync service) it makes the plugin less useful.

(First, it's an incredible plugin, thanks for your amazing work!)

• As the question says is it possible to automatically rename the source file?
  • I know I can change the name in the UI, but the source file keeps the same and I didn't find where it store the name information.
  • And I found that I can manually change it without losing my data, but once I make further modifications on the sheet, it will create a new file with the original name.
• I want to make sure all the stored files are at use, otherwise they can be deleted safely.

Hi! I've happily been using the Luckysheet Logseq plugin, which I like very much apart from one thing: this plugin tends to lose data.

I understand that for performance reasons it writes to temporary files and syncs with the child block markdown only on the next app start, but this process is not entirely reliable and I have lost hours of work on a few occasions. Plus I sync my Logseq graph on multiple devices, and Luckysheets aren't part of that sync unless I close and reopen Logseq everytime, which is cumbersome and slow.

How about a "save" button that syncs with the child block markdown when clicked? This way the plugin keeps its current performance profile, and would also provide data safety.

从logseq 0.6.0版本开始，我在电脑上装了luckysheet，尝试很多版本（无论是logseq还是 lucksheet 官网每发布一个新版本，我都会尝试安装一次，希望能用上luckysheet），logseq命令菜单就是没有lucksheet。我的系统是window10，logseq0.6.7，luckysheet0.6.1。

根据说明，我在'.logseq\storages\logseq-luckysheet'中找到的保存的表格文件，文件被保存为类似‘workbook-9f303b8837ccde59ad8016a901a3e8e1b874643e’形式。

1. 尝试过增加文件后缀xlsx，打开失败。
2. luckysheet项目提供的在线工具仅支持xlsx文件。

请问有没有方法可以读取插件自动保存的表格文件？感谢您的插件，给笔记带来了很棒的体验！！！

Hi,

Thank you very much for the plugin!

I use the desktop version of Logseq 0.75 on macOS.

After a reindex I get the following error: 数据读取错误！

When I printed the error that comes out of the exception (document.getElementById("sheet").innerHTML = '<p class="error">数据读取错误！' + err + '</p>' ;) I go the following:

SyntaxError: Unexpected token ` in JSON at position 69265

The issue is in this line:

JSON.parse(firstChild.content.substring(7, firstChild.content.length - 3)),

I'm not sure whether it's a CR/LF/encoding issue, but for me the correct index is not -3, but -4.

I locally replaced the line with the issue with the following to patch the issue:

JSON.parse(firstChild.content.substring(7, firstChild.content.lastIndexOf(']') + 1)),