Support composite primary keys on show, edit, update and destroy actions #2645
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impressively, this seems to be all that's required to support composite primary keys in Rails 7.1
Description
Support composite primary keys on show, edit, update and destroy actions on Rails 7.1.
params.extract_values
was introduced in Rails 7.1.0.beta1.Checklist:
Screenshots & recording
Not really.
Manual review steps
We do have a model that uses 3 enums as primary keys and I was able to view it's show page, edit and update it after the change. To implement the change in our codebase we have overwriting
set_record
on each resource that has a composite primary key.