Skip to content

Conversation

@ksdcsk
Copy link

@ksdcsk ksdcsk commented Mar 6, 2020

Regular paths added to the FileViewFinder class are resolved (i.e.converted to absolute paths), but hinted paths are not (stored in $hints). It would be logical and coherent to apply the same standard to all paths.

What brings me to propose this pull requests is issue #31789. The problem is that vendors might register their views paths using the addNamespace method by passing a relative path, that will be later used by other classes as provided. When views are cached, the path to the view matters, as its hash is used to identify the view. This pull request would solve some variations of that bug such as those described here.

All tests were passed in my local environment.

@ksdcsk ksdcsk changed the title FileViewFinder: Resolve hinted paths [7.x] FileViewFinder: Resolve hinted paths Mar 6, 2020
@taylorotwell
Copy link
Member

No plans to change this code right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants