fix: single meta field edge case #257
Merged
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
preda-bogdan
approved these changes
Mar 1, 2024
|
🎉 This PR is included in version 32.0.12 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
pirate-bot
added
the
released
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.
Summary
Fixes the case when only one meta field is added. Now when the
$ppom->meta_idis not an array it is instantiated with an array containing the id.Will affect visual aspect of the product
NO
Screenshots
Now it works with both a single and multiple meta fields: https://vertis.d.pr/i/FWauH4, https://vertis.d.pr/i/yXfM03 .
Test instructions
Attach only one ppom meta field to a product, the meta field should be displayed.
Closes #256.