fix: export table event type from gantt package#5201
Open
biubiukam wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤔 This is a ...
🔗 Related issue link
fix #4320
💡 Background and solution
@visactor/vtable-ganttalready exposes the nestedVTablenamespace, but the package entry did not directly export the ListTableTABLE_EVENT_TYPEconstants.This PR re-exports
TABLE_EVENT_TYPEfrom the Gantt package entry and adds a regression test to keep the top-level export aligned withVTable.TABLE_EVENT_TYPE.📝 Changelog
@visactor/vtable-gantt.@visactor/vtable-gantt导出 ListTable 事件类型常量。☑️ Self-Check before Merge
🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough