feat: include relation in NestedParams #16
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Base automatically changed from
support-for-updating-nested-action-types
to
main
March 27, 2023 08:08
For certain middleware it is necessary to reference the relation for that nested action. For example instead of deleting a toOne relation a soft delete middleware may decide instead to unlink the relation and update it to have a deleted mark which would require both the isList and the foreign key information stored on the relation.
olivierwilkinson
force-pushed
the
include-relation-information-with-nested-params
branch
from
ff3c514 to
f926d3d
Compare
olivierwilkinson
deleted the
include-relation-information-with-nested-params
branch
|
🎉 This PR is included in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For certain middleware it is necessary to reference the relation for that nested action. For example instead of deleting a toOne relation a soft delete middleware may decide instead to unlink the relation and update it to have a deleted mark which would require both the isList and the foreign key information stored on the relation.