[#1725] VaSplit component implementation - #2068
Conversation
m0ksem
left a comment
There was a problem hiding this comment.
Would be nice to have real-world example (like Sidebar and App content.)
Have you tested this on phone? You will need to listen for touchstart, touchend events.
rustem-nasyrov
left a comment
There was a problem hiding this comment.
Looks awesome! I have a little suggestion: if the cursor goes out of the splitter container we lose the 'draggable' state, would be better if the user can move the splitter out of the container.
fix:minor fix fix:redundant limits prop changed to number
fix:minor fix fix:redundant limits prop changed to number
feat:added resize observer to the container (to recalc limits) feat:docs updates
fix: review fixes
# Conflicts: # packages/docs/src/locales/en/en.json # packages/docs/src/locales/ru/ru.json
|
From discussion with Vitaly:
|
| }) | ||
|
|
||
| switch (measureValue) { | ||
| case '%': |
There was a problem hiding this comment.
We have to parse value anyway. So, this suggestion isn't suitable in my opinion.
| case '': | ||
| return 100 | ||
| default: | ||
| warn('Invalid limits measure!') | ||
| return 0 |
There was a problem hiding this comment.
default:
if (v !== Number(v)) warn('puk')
|
Can we also have some specs like this? We will put it later under documentation page. It takes too much time to understand how it works... |
fix: review suggestions refactor: minor docs refactor
fix: minor demo fix
Close: #1725
Description
New split component implementation.
Types of changes