useRowState seems to have a logical error

[bradennapier]

Since I am clearly just showing in your code exactly where the issue is, skipping the template there.

At the moment using the useRowState seems to have some bugs in the initialAccessor logic for both row and cell states.

https://github.com/tannerlinsley/react-table/blob/master/src/plugin-hooks/useRowState.js#L156

Documentation says:

initialRowStateAccessor: Function(originalRow) => Object<any>
Optional
Defaults to: row => ({})
This function should return the initial state for a row.
If this function is defined, it will be passed a Row object, from which you can return a value to use as the initial state, eg. row => row.original.initialState
initialCellStateAccessor: Function(originalRow) => Object<any>
Optional
Defaults to: cell => ({})
This function should return the initial state for a cell.
If this function is defined, it will be passed a Cell object, from which you can return a value to use as the initial state, eg. cell => cell.row.original.initialCellState[cell.column.id]

So while the type shows originalRow - the description indicates it would give the row or cell object (which is probably what it should be since its fairly useless for every sell to get the original row without knowing any information about itself even anyway. That should only be executed a single time if that is the case.

Seems that both the row and cell should indeed receive the row or cell object as the docs indicate rather than the raw originalRow value being sent. At this point I can not see any purpose to using initialCellStateAccessor

[picosam]

Hello @tannerlinsley, is this a verified bug?

[tannerlinsley]

🎉 This issue has been resolved in version 7.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀