Closed ngdangtu-vn closed 8 months ago
I think I can work on this if my proposal got approved.
I'd rather not add any breaking changes to Tui 2
right now, unless completely necessary.
I'm slowly working on Tui 3
and it'd most likely become wasted work when it releases.
I'm sorry but what do you mean "wasted work"? Do you already have a new table component in Tui 3
?
Tui 3
API will be completely different from current one, and for the most part components won't be able to be reused.
That's cool, my app is not too big so I don't mind to migrate to newer version. But coming from CSS background, I really like to use the term "border". Do you mind if I suggest it for Tui 3
? The term "frame" can be useful for other case so it is kinda waste to use it on visual feature like table border.
Nice
already uses the term border, and it will translate its way to Tui 3
What this feature is meaning to achieve
Better developer experience by offering description that be easy to understand, and new options to improve the lib quality.
Solution
Note: 1 & 2 is connected to each other. If you want to keep the term 'frame', we can ignore 2. But if you think 'border' is a good term, we should update 2 as well.
TableOptions.charMap
toTableOptions.borderStyle
. I believe it will help dev who try to modify the border understand where to look for.TableOptions.theme.frame
toTableOptions.theme.border
.TableOptions.charMap
should have an optionnone
to completely remove border.Describe alternatives you've considered
For suggestion 3, I set
crayon.hidden
intheme.frame
for now. But I think it make more sense inTableOptions.charMap
right?I trid the
GridLayout
in replace of no broder but it doesn't feel right when I have a table data and use grid on it.