fix: onChange can also update other fields

[wojtek-krysiak]

@Co0sh there was an error where users couldn't update properties with onChange.

Baicaly this component didn't work:

import React from 'react'
import { EditPropertyProps } from 'admin-bro'
import { Button, Box } from '@admin-bro/design-system'

const ValueTrigger: React.FC<EditPropertyProps> = (props) => {
  const { onChange, record } = props

  const handleClick = (): void => {
    onChange({
      ...record,
      params: {
        ...record.params,
        name: 'my new name',
      },
    })
  }

  return (
    <Box mb="xxl">
      <Button data-testid="name-button" type="button" onClick={handleClick}>Set Name</Button>
    </Box>
  )
}

export default ValueTrigger

Name property is a string and inside there is an inner state which was only updated from the external params on component mount.

I've fixed that and will merge it, but please verify if this is ok.

[wojtek-krysiak]

removed usePrevious because the previous state is in value

[wojtek-krysiak]

added that which invalidates when external param was updated

[github-actions]

🎉 This PR is included in version 3.1.0-beta.4 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀