Ensure that decode returns all parts of composite key #71
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.
This pull request addresses a bug in the decoding of composite keys. In the current implementation, when a model is defined with a composite primary key, the decoding process incorrectly strips out the first key component. This fix ensures that all components of the composite key are retained and correctly decoded.
For models with composite keys, such as the following example:
The decode_prefix_id method fails to decode the composite key correctly. Specifically, when decoding the prefix_id for a Product instance, the resulting composite key array incorrectly omits the first key component.
Example to illustrate the issue:
Currently, the
composite
array is:However, the expected result should be:
This fix ensures that the decode_prefix_id method properly handles composite keys, preserving all components as intended.