fix(core): pass meta params from useDeleteButton to useButtonCanAccess#7289
Conversation
🦋 Changeset detectedLatest commit: 438205f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
alicanerdurmaz
left a comment
There was a problem hiding this comment.
Hi, thanks for improving Refine.
Everything looks great except changeset file names should be auto-generated.
c684655 to
1a8a596
Compare
|
Hi @alicanerdurmaz, thanks for the review! I've made the following changes: Changeset filename is now auto-generated using changeset add delete-button |
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
useDeleteButton does not pass the meta prop to useButtonCanAccess. This causes custom access control rules that rely on meta params to fail when checking permissions for the delete button.
What is the new behavior?
useDeleteButton now correctly forwards props.meta to useButtonCanAccess, matching the pattern already used in useNavigationButton.
Fixes #7285
One-line fix. useNavigationButton already passes meta correctly, so this change brings useDeleteButton in line with that existing pattern.