Allow getter hooks to reuse the previous props

I’m digging into the getter hooks, like the getCellProps etc. — what I’m wondering is if it is somehow possible right now to access the previous values of the props, in order to manually merge/reuse them?

Example: I want to access the current colSpan, and add some styles based on it or modify it. But from what I’ve seen, this is not possible from the hooks. If I’m not missing something, then I can see this could be added in one of the following ways:

1. Getter hooks could have the third argument after the Cell and TableInstance, which would contain the currently accumulated props.

2. Alternatively, the currently accumulated props could be probably stored inside a Cell?

Currently, I can see that the only way of doing what I want is outside of a plugin-hook, by using the cell.getCellProps() during the Table generation and passing its values to my other function. But I feel that having a way to access the props from the previous hooks could be very powerful and could allow to create quite flexible plugin-hooks 😃

[tannerlinsley]

The most important parts are how the prop getters work:

// Auto extend with smart-merging styles and classNames
hooks.getThingProps.push({
  newProp: true,
})

// Multi auto extend with smart-merging styles and classNames
hooks.getThingProps.push([{
  style: {...},
  className: 'one'
}, {
  style: {...}, 
  className: 'two'
}])

// Functional replacement with both options above:
hooks.getThingProps.push((props, instance, row) => [
  props,
  {
    style: {...}, 
    className: 'two'
  }
])

// This will ditch old props
hooks.getThingProps.push((props, instance, row) => [
  // props,
  {
    style: {...}, 
    className: 'two'
  }
])

// This will do defaults
hooks.getThingProps.push((props, instance, row) => [
  {
    style: {...}, 
    className: 'two'
  }
  props,
])

// This will replace all props without smart merging
hooks.getThingProps.push((props, instance, row) => [
  {
    ...props,
    style: {...}, 
    className: 'two'
  }
])

More importantly, all of these options are also supported via the actual resulting prop getter function on the instance. So you should never need to use mergeProps either (which is also why it’s deprecated now 😉)

[tannerlinsley]

I have a pretty decent solution that will fit all of these use cases. I’m currently working up a PR. Hang tight.