[6.x] Fix augmentation of Status Log fieldtype when using Database Orders #1014
Conversation
This file contains 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
duncanmcclean
deleted the
fix/status-log-augmentation-with-database-orders
branch
|
Released as part of v6.0.6. |
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.
In #983, I changed it so the order status log is stored in a separate database table from the actual orders for querying/performance reasons.
However, in testing something else, I realised that after that change, the
HasManyrelationship was being passed in as the$valueto the Status Log fieldtype'saugmentmethod which caused an issue when trying to augment the status log since it's expecting an array of arrays instead.This PR fixes that by transforming the
HasManyrelationship into the right format of arrays that the fieldtype can augment.