Skip to content
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

🐛 明细表,排序问题,排序在空值处断开 #2707

Closed
1 task done
NoobNotN opened this issue May 10, 2024 · 3 comments · Fixed by #2708
Closed
1 task done

🐛 明细表,排序问题,排序在空值处断开 #2707

NoobNotN opened this issue May 10, 2024 · 3 comments · Fixed by #2708
Assignees

Comments

@NoobNotN
Copy link
Collaborator

🏷 Version

Package Version
@antv/s2
@antv/s2-react
@antv/s2-vue
见 sandbox

Sheet Type

  • TableSheet

🖋 Description

明细表排序失败,排序会在某些位置断开
image

⌨️ Code Snapshots

🔗 Reproduce Link

https://codesandbox.io/p/sandbox/fancy-cdn-ptzpr5

🤔 Steps to Reproduce

😊 Expected Behavior

😅 Current Behavior

💻 System information

Environment Info
System
Browser
@lijinke666 lijinke666 self-assigned this May 10, 2024
@lijinke666 lijinke666 added the 🐛 bug 这个是一个 bug label May 10, 2024
Copy link
Contributor

你好 @NoobNotN,很抱歉给你带来了不好的体验, 我们会尽快排查问题并修复, 请关注后续发布日志.

Hello, @NoobNotN, We are so sorry for the bad experience. We will troubleshoot and fix the problem as soon as possible. Please pay attention to the follow-up change logs.

lijinke666 added a commit that referenced this issue May 11, 2024
* fix: 修复明细表含有空数据占位符时排序错误 close #2707

* test: 单测修复
lijinke666 added a commit that referenced this issue May 11, 2024
* fix: 修复明细表含有空数据占位符时排序错误 close #2707

* test: 单测修复
@lijinke666
Copy link
Member

🎉 This issue has been resolved in version @antv/s2-v1.55.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@lijinke666
Copy link
Member

🎉 This issue has been resolved in version @antv/s2-v2.0.0-next.20 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants