Allow specifying effective path for a view renderer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with the withRenderers configuration and review issue #289 for the existing renderer-selection behavior. Examine the proposed yiisoft/strings WildcardPattern utility and assess matching performance before defining the path-based behavior. Done means renderers can be selected by effective view path as well as extension, with coverage for the shown wildcard case.
Written by the indexing model from the issue text.
Description
Proposed new feature or change
An ability to match the renderer not only by extension but also based on the view path:
->withRenderers([
'**payments**.blade.php' => new PhpTemplateRenderer(),
]);
https://github.com/yiisoft/strings/blob/2.x/src/WildcardPattern.php could be used for wildcards support.
Need to consider performance before implementing it.
See #289
- Dominant language
- PHP
- Stars
- 57
- Forks
- 47
- Avg merge
- 46m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yiisoft/view
-
Increase MSI to 100% Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·