Skip to content

Refresh the doc tree after data sync generates conflicting documents #11137

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

Closed
3 tasks done
h9485910 opened this issue Apr 25, 2024 · 3 comments
Closed
3 tasks done

Refresh the doc tree after data sync generates conflicting documents #11137

h9485910 opened this issue Apr 25, 2024 · 3 comments
Assignees
Milestone

Comments

@h9485910
Copy link

h9485910 commented Apr 25, 2024

PC端冲突文档不能及时在文档树显示

Is there an existing issue for this?

  • I have searched the existing issues

Can the issue be reproduced with the default theme (daylight/midnight)?

  • I was able to reproduce the issue with the default theme

Could the issue be due to extensions?

  • I've ruled out the possibility that the extension is causing the problem.

Describe the problem

本来是想测试下同步冲突了会怎么样,PC端开启了冲突后生成冲突文档,云端同步冲突后,文档树不能实时显示生成的冲突文档,重建索引后才在文档树显示

Expected result

生成的冲突文档能够及时显示

Screenshot or screen recording presentation

20240425152430

Version environment

- Version: 3.0.11
- Operating System: win 11
- Browser (if used):

Log file

emmmm,很容易复现就不用贴日志了吧

More information

No response

@88250
Copy link
Member

88250 commented Apr 25, 2024

这个不需要重建索引的,只需要重新展开文档树。

@h9485910
Copy link
Author

这个不需要重建索引的,只需要重新展开文档树。这个不需要重建索引的,只需要重新展开文档树。这个不需要重建索引的,只需要重新展开文档树。

不能优化下直接展示吗?还需要手动操作一下感觉不够人性化,对于不了解的用户也是一个认知障碍

@88250
Copy link
Member

88250 commented Apr 25, 2024

嗯,后续考虑自动刷新一下。

@88250 88250 self-assigned this Apr 25, 2024
@88250 88250 changed the title PC端冲突文档不能及时在文档树显示 Refresh the doc tree after data sync generates conflicting documents Apr 25, 2024
@88250 88250 added this to the 3.0.12 milestone Apr 25, 2024
88250 added a commit that referenced this issue Apr 25, 2024

Verified

This commit was signed with the committer’s verified signature.
@88250 88250 closed this as completed Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants