Benjamin Cripps

@jkganzan13 I've add the header action, which will work when you call the following action: ``` js store.dispatch( Actions.GridActions.setHeaderVisibility({ stateKey: 'unique', hidden: true }) ); ``` I will publish a...

The `ROW_EXPANDER` plugin hasn't been implemented yet :/ so this functionality doesn't currently exist. I will mark this as help wanted and get to it as soon as I can.

Just curious, does setting expandable on the nodes which do/dont need to be expandable solve this problem for you?

Right now the only way to configure the order of columns is to pass them in the order you'd like them displayed. However, that the menu column is being displayed...

In this scenario, since your keys are not **unique** you shouldn't be specifying the `createKeyFrom` property. Grid will create unique keys by default (it just won't be as performant).

That should work, but you could also not pass in the property at all. I believe it defaults to false.

Any update on this?

I think ```JS plugins: { KEYBOARD_NAVIGATION: { enabled: true } }; ``` is probably the way to go. Let me know if you run into any issues!

I think if you take a look at the simple example, you should find what you need. This uses locally paged data.

Are you loading data async or simply passing data as props?