fix: preserve row id in meta - #6925
Conversation
🦋 Changeset detectedLatest commit: 86dd86c 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 |
✅ Deploy Preview for refine-doc-live-previews ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @pokycookie thanks for the PR. Can you add patch changeset? You can see our contributing guide here. |
BatuhanW
left a comment
There was a problem hiding this comment.
Hey @pokycookie thanks for the PR.
Don't forget to add changesets next time.
|
Hi @BatuhanW, Do you know when a new released will be launched with this fix? |
|
Hi @BatuhanW, Thanks for the review and merge! I’m sorry I missed the changeset. This was my first contribution to refine. |
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
When editing a row inside an Edit page, the audit log payload’s meta.id reflects the Edit page’s route id (e.g. 6) instead of the edited row id (e.g. 1). This is reproducible with the sample in the issue.
Root cause: In audit logging, the meta object is composed such that route/context meta (including id) is spread after the explicit id/ids, which overrides the intended row id.
What is the new behavior?
Adjust the meta composition order in audit logging so explicit id/ids take precedence over the combined meta from route/context.
Changes:
{ ...rest, dataProviderName, id }{ ...rest, dataProviderName, id }{ ...rest, dataProviderName, id }{ ...rest, dataProviderName, ids }This keeps the rest of the application behavior intact, only affecting the audit log payload.
fixes #6906
Notes for reviewers
Touched files:
Tests
(before)

(after)
