Fix array access on new type Int #59
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
|
Ah yes, sorry for the oversight! Thank you for the PR |
|
Ah yes, sorry for the oversight! Appreciate the PR! |
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.
This is simply a follow-up on our last exchange! This one slipped my attention, but there were some array access on imageId and videoId still in the Recipe model.
If I understand right, the array accesses still found around line 162 in fields/Recipe.php should stay since it comes from the admin input and the input accepts arrays regardless of the limit of 1... I think. 🤔 https://github.com/nystudio107/craft-recipe/blob/develop-v4/src/fields/Recipe.php#L162