You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a table where I would like to have some content overflow from a row. However, passing a rowStyle object with overflow: 'visible' can't do it, because the Table component merges the rowStyle object with some other styles (including overflow: 'hidden') here.
We use css in js everywhere in the project, so using a className to override this would be a little inconsistent and confusing.
So I was wondering what the reasoning behind forcing default some styles is?
@wuweiweiwu having overflow: visible seemed to work for me, the layout looked the same, and the height was properly set.
Either way, I feel like it would make sense to allow users to override these default styles when passing in a style object since they can do the same with a class.
I have a table where I would like to have some content overflow from a row. However, passing a
rowStyle
object withoverflow: 'visible'
can't do it, because theTable
component merges therowStyle
object with some other styles (includingoverflow: 'hidden'
) here.We use css in js everywhere in the project, so using a className to override this would be a little inconsistent and confusing.
So I was wondering what the reasoning behind forcing default some styles is?
I would suggest changing this
To this
To give users the option to override the styles if they want, while still keeping the defaults if they don't override them.
If you guys agree to this change, I'm more than happy to submit a PR for it!
The text was updated successfully, but these errors were encountered: