-
Notifications
You must be signed in to change notification settings - Fork 9
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
671 [Pivot Table] Droppable #690
Conversation
Codecov Report
@@ Coverage Diff @@
## master #690 +/- ##
==========================================
+ Coverage 98.58% 98.60% +0.01%
==========================================
Files 475 476 +1
Lines 4108 4161 +53
Branches 636 631 -5
==========================================
+ Hits 4050 4103 +53
Misses 58 58
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tá 🔝
Só alguns detalhes
-> Adding i18n to droppable messages -> Fixing droppable stories -> Adding a check for filterState and handleFilterUpdate props
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Just commented some points to review. Also, why did you put these components inside the PivotTable context? I think it can be really useful outside this component too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
I just commented some things that could be different.
The change of context happened because we have some doubts about the final result from issue #657. Who use the Bold will call a one component called For now we don't have answers for these questions (suggestions are welcome). I wrote in the issue about this and create a note in the team board too. So these change of context could be rolled back in the future :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just left one doubt after the fixes. Good job!
const { name, keyState, keyMapping, accept, filter, handleKeyUpdate, onKeyNav } = props | ||
|
||
const locale = useLocale() | ||
|
||
const [{ isOver }, drag] = useDrop({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic that throw error in some scenarios isnt more necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second check is no longer necessary because DroppableFilter
ensures that filterState
and handleFilterUpdate
must be defined together.
In relation to the first, it remains necessary. I will fix this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting the fix from this comment
Part of #657
closes #671