NikolayNIK
Remove default scrollbar style values
A few days ago I've decided to drop my old local version of material_table_view (it was based on v3.2.1) and use the releases available on pub. It looks great! Thanks!
I just noticed that default behavior of scrollbar for table view is different from what Flutter's own scrollbar behavior and found that you're using some default values in ResolvedTableViewScrollbarStyle that's causing this issue. I think it's better to keep values as null if nothing is provided by user.
Deploy Preview for visionary-chimera-cb5753 ready!
| Name | Link |
|---|---|
| Latest commit | 7b0a5f89de2869b7687146f6edcbd550ec648592 |
| Latest deploy log | https://app.netlify.com/sites/visionary-chimera-cb5753/deploys/65fffa33d019b800083eff56 |
| Deploy Preview | https://deploy-preview-15--visionary-chimera-cb5753.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
It's nice to see you here again and thanks for the kind words.
Those default values are there to keep compatibility with older versions of the library that used these values because I've deemed them the most appropriate for my use case.
That said, using default Flutter values is probably a safe bet. Especially when there is no way to use them otherwise.
However, that change would break the contract between library and its users that use these default values for similar use cases to mine. I have no idea if it is worth it or not. At the very least it is going to require a major version change to indicate the contract change, which means the change is going to have to wait for a while for other breaking changes to pile up.
Be sure to let me know if this is something needed sooner rather than later.
Your concerns regarding the breaking change is completely valid and understandable. I'm once again using my own version containing this change. @NikolayNIK