Path reference fix #102
Closed
Path reference fix #102
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
…enced path objects.
…tion - dynamic attribute array references were not resolving, producing an E_NOTICE.
|
Thank you! |
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.
If referenced path object contained a common referenced parameters, reference resolution for path object would produce an E_NOTICE due to indirect dynamic property modification attempt. If silenced or ignored, the resulting object would still be able to return expected results, but references would not be actually resolved.
Path object in v3 has only one array property which can contain references (common parameters).
Updates to test vendor references had to be done to pass all green.
The same problem was already addressed recently #87.
Would be great to have a patch release if this get to be merged!