tannerlinsley

7 ms·

1. 31.▲
   by tannerlinsley 7y ago

   You can control the table from wherever you can put the `useTable` hook. 99% of the time this will be in your table component, but nothing is stopping you from hoisting this higher or decorating it with whatever other logic you want. Even i
2. 32.▲
   by tannerlinsley 7y ago

   It's a codesandbox bug. Log in with github for now to bypass the error.
3. 33.▲
   by tannerlinsley 7y ago

   The beginning of your comment made me uneasy, but then you endorsed the library! Phew! Thanks!
4. 34.▲
   by tannerlinsley 7y ago

   bug
5. 35.▲
   by tannerlinsley 7y ago

   Looks like a but with Codesandbox. I believe if you log in, it will bypass this bug. I'm speaking with CS about it as we speak.
6. 36.▲
   by tannerlinsley 7y ago

   DM me on twitter and we can discuss more there. @tannerlinsley
7. 37.▲
   by tannerlinsley 7y ago

   A plugin is currently in development to make this extremely easy and turn-key, but for now (since you control the rendering layer), you can do this on your own with a few lines of code in your table renderer.
8. 38.▲
   by tannerlinsley 7y ago

   At a glance features: - Lightweight (5kb - 12kb+ depending on features used and tree-shaking) - Headless (100% customizable, Bring-your-own-UI) - Auto out of the box, fully controllable API - Sorting (Multi and Stable) - Filters - Pivoting
9. 39.▲
   React Table v7 – Hooks for building fast and extendable data grids in React(github.com)

   136 points by tannerlinsley 7y ago|40 comments
10. 40.▲
    React Query Devtools(github.com)

    2 points by tannerlinsley 7y ago|0 comments
11. 41.▲
    React Query Devtools(twitter.com)

    2 points by tannerlinsley 7y ago|0 comments
12. 42.▲
    by tannerlinsley 7y ago

    That's awesome! Soo cool to see it in your product! About being nervous, I don't think you should be! I know it's intimidating moving to v7 from v6, but it's pretty simple given the examples that we have in the repo thus
13. 43.▲
    by tannerlinsley 7y ago

    I'm sorry you've had that experience, though I don't recall seeing any issues on Github to this degree that we haven't taken care of. Can you point me to anything specific I can help you out with? Thus far, React Table v
14. 44.▲
    by tannerlinsley 7y ago

    The force is strong with this one! Thanks!
15. 45.▲
    by tannerlinsley 7y ago

    I wrote React Table and have never heard of those. So no, React Table is not a reimplementation.
16. 46.▲
    by tannerlinsley 7y ago

    If you are not operating within the React Framework, I can totally agree with this. I used Ag-Grid before I built React Table and it shines as a JS-only datagrid. Start using React however, and I don't believe that is the case.
17. 47.▲
    by tannerlinsley 7y ago

    I would actually say that if you like React-Table, you likely wouldn't want to use Ag-Grid for the very reasons that React Table exists. Had someone asked if there were similar tables libraries, I would have expected this response and
18. 48.▲
    by tannerlinsley 7y ago

    I'm terribly sorry that you ended up in Canvas land for tables. I built and maintained Chart.js for a while, so I know how hard it can be to work with. As for React Table, I have never run into a situation where drawing a table to canv
19. 49.▲
    by tannerlinsley 7y ago

    - React Table is not an HOC - React may still show educational materials about HOC's but hooks replace their use-cases in almost every situation. - I don't see how HOC's are attempting to draw more separation of concerns betw
20. 50.▲
    by tannerlinsley 7y ago

    Yep! You're getting it now! Take a look at the examples and see just how easy it is to spin up your own table with React Table :)
21. 51.▲
    by tannerlinsley 7y ago

    I would say the "separation of concern" you're referring to is typically centered around (and definitely grew out of) the idea that styles, logic and markup should be in separate files or logical systems (html, css, js). The
22. 52.▲
    by tannerlinsley 7y ago

    By team, I think you mean me. I'm flattered! :) Being a headless UI library doesn't necessarily mean that it has no business being in charge of your UI, it's more about the way that you interact with the API. If you look clos
23. 53.▲
    by tannerlinsley 7y ago

    I've toyed with that idea for a long time now. I go back and forth, but as of today, I don't feel like that would do much good with the success I've seen people having with the examples. Sure, v6 was popular because it was ve
24. 54.▲
    by tannerlinsley 7y ago

    So does React-Form ;) https://github.com/tannerlinsley/react-form
25. 55.▲
    by tannerlinsley 7y ago

    That's very strange. Can you file an issue or send me more info on how to replicate that issue?
26. 56.▲
    by tannerlinsley 7y ago

    Thanks! Be sure to get your company to sponsor me on Github if you can!
27. 57.▲
    by tannerlinsley 7y ago

    This is how I envisioned things from the beginning. Some people may want a quick drop-in library, since that's what they're used to, but in reality, copying and pasting an example into a `component/Table.js` file is essential
28. 58.▲
    by tannerlinsley 7y ago

    - Exporting to excel is simple. You are provided the final data model after all processing/filtering/sorting/etc is done, and you are free to use whatever means you want to provide that data to your users, eg. The 'xlsx&
29. 59.▲
    by tannerlinsley 7y ago

    "Plain old HTML" is great. And guess what, because React Table is headless, you can render your tables using standard HTML table elements (table,thead,tbody,tr,th,td,tfoot,etc...). Html elements on their own, however, are not capa
30. 60.▲
    React Hooks, the Rebirth of State Management and Beyond(medium.com)

    1 points by tannerlinsley 8y ago|0 comments