[DataGrid] Prepare work for a future public state api

[dtassone]

Add the state API that allows using the grid in a controlled way. Related to #190.

[oliviertassinari]

I think that we miss:

• The declarative API, this one should come first.
• The documentation.
• End to end tests.
• A description of the problem we are solving.

[dtassone]

I think that we miss:

• The declarative API, this one should come first.
  What do you mean?

• The documentation.
• End to end tests.
• A description of the problem we are solving.

[oliviertassinari]

What do you mean?

• Looking closer, it might be handled, I think that I will wait to see the documentation and the tests to be sure.
• I assume we miss a prop to set the default state, should it be handled in a different pull request, later on?
• On a related, the controllable API of react-table is puzzling me. I have never seen such a pattern before. I don't understand the incentive for having a prop that expects a state function (oldState => newState). Strange. It seems to have been introduced in Override internal table state (beta 26) TanStack/table#1704. I don't see any completing argument in the thread. So, I think that we can continue in the direction we have started, and ignore it.

[oliviertassinari]

For the documentation, I think that a new page would probably be the best solution. I don't see another place where documenting this really makes sense. We could maybe have a "Data & state" page, where we document the state, how to load data, lazy loading, the server-side part,

[oliviertassinari]

no 📚 = nobody uses it

[oliviertassinari]

Agree with Danail, exposing the state to the open raises the question of what's internal and not. Let's have all new features be documented. This is a forcing function to consider the feature end-to-end.

[dtassone]

Agree with Danail, exposing the state to the open raises the question of what's internal and not. Let's have all new features be documented. This is a forcing function to consider the feature end-to-end.

This is to allow to persist the state, attach it to a redux store, or just manipulate the grid state directly.

[oliviertassinari]

This is to allow to persist the state, attach it to a redux store, or just manipulate the grid state directly.

Will it work? I am right to assume that we can't have developers store internal values that we might change between two release patches, breaking the restore logic?

[dtassone]

This is to allow to persist the state, attach it to a redux store, or just manipulate the grid state directly.

Will it work? I am right to assume that we can't have developers store internal values that we might change between two release patches, breaking the restore logic?

Well that's the reason to expose the state, so we allow users to persist and restore their settings for columns...
After yes we are going to have to migrate states between changes...
Happy to close the PR if you don't want it

[oliviertassinari]

What about we isolate the private state from the public state? For instance in https://codesandbox.io/s/material-demo-forked-0n563?file=/demo.js, developers would end-up sending a lot of unneeded data through the network, e.g. send the rows multiple times, which doesn't scale for large datasets.

[dtassone]

What about we isolate the private state from the public state? For instance in https://codesandbox.io/s/material-demo-forked-0n563?file=/demo.js, developers would end-up sending a lot of unneeded data through the network, e.g. send the rows multiple times, which doesn't scale for large datasets.

I would leave it this way for now

• You don't need to restore the full state, as we do a merge internally
• We won't document it or we will put a warning that this can change
• We spend enough time on the state
• This is just the first version we can improve it later
• It is used internally so breaking it in pieces would mean another set of big refactoring, and state should only be stored in 1 place. (Single source of truth)

[oliviertassinari]

Ok, I have updated the title of the pull request, it's internal, for now, but it sets the stone in the right direction.