feat: add extra arg in onSuccess, onError

[Lee-sungheon]

Hi!
While using swr 2.0, I felt uncomfortable that extgraArg could not be used in onSuccess and onError.
So I suggest you can use extraArg in onSuccess and onError like this

async onSuccess(data, key, config, extraArg) {
  ...

  await mutate('otherKey', extraArg.pk);
},
async onError(error, key, config, extraArg) {
  ...

  await mutate('otherKey', extraArg.pk);
},

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[promer94]

I realize there is a alternative way to achieve this.

const { trigger, isMutating } = useSWRMutation('/api/user', sendRequest)
trigger(arg, { onSuccess: () => {
   mutate('other key', arg)
}})

You could config onSuccess by trigger. It's more flexible.

Would this solve your problem ?

[Lee-sungheon]

Good alternative way but I want to create a custom hook using useSWRMutation.

When a custom hook is created in a way that uses a trigger, not only does the code become complicated, but it also becomes difficult to further customize the trigger.

export const useSendRequest = () => {
  const { trigger, ...others } = useSWRMutation('/api/user', sendRequest)
  const myTrigger = (arg) => trigger(arg, { onSuccess: () => {
    mutate('other key', arg)
  }})

  return {
    trigger: myTrigger,
    ...others
  }
}

However, when a custom hook is created as follows, not only the readability of the code is improved, but also the trigger is additionally customizable.

export const useSendRequest = () => {
  return useSWRMutation('/api/user', sendRequest, {
    onSuccess: (data, key, config, extraArg) => {
      mutate('other key', extraArg)
    }
  })
}

[Lee-sungheon]

@huozhi @shuding @promer94
Can you check the PR?
This is a must-have feature for me.