Closed didoshakra closed 2 years ago
Yes it appears typing in the global filter is changing the canFilter prop to true on disabled columns. Is this a bug or just something I'm not understanding in the docs?
This issue is being marked as stale (no activity in the last 14 days)
This issue has been detected as stale and automatically closed. It's very likely that your issue has remained here this long because it would require breaking changes to v7. React Table v8 is currently in alpha (soon beta!) and already contains bug fixes, performance improvements and architectural changes that likely address this issue.
react-table v7. I want to use react-table in my future projects written with Next.js. I'm trying to create a table that has sorting, fottert, filtering, row-selected, paginations and fixed head and footer. Based on the examples https://react-table.tanstack.com/docs/api/useFilters, I have already created a table that has sorting, fottert, filtering, row-selected. But here I have a not very important nuance that I can not overcome. When maintaining the value of the global filter in the select header appears filter input by columns. It seems that somewhere it gives properties canFilter: true. I can overcome it. Maybe you need to add another condition to the code: