ENH Update code to reflect changes in template layer #265
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
Closed
23 tasks
GuySartorelli
force-pushed
the
pulls/6/refactor-template-layer
branch
from
3b46bb9 to
94bd9e0
Compare
GuySartorelli
commented
Oct 23, 2024
Comment on lines
-168
to
+171
| $template = SSViewer::fromString($config->ReviewBody); | ||
| $value = $template->process(ArrayData::create($variables)); | ||
|
|
||
| $engine = Injector::inst()->create(TemplateEngine::class); | ||
| $value = $engine->renderString($config->ReviewBody, ViewLayerData::create(ArrayData::create($variables))); |
There was a problem hiding this comment.
Use TemplateEngine instead of explicitly SSTemplateEngine because ReviewBody could be updated to contain whatever syntax the devs wanna use.
emteknetnz
approved these changes
Oct 30, 2024
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.
Relies and reflects on changes in silverstripe/silverstripe-framework#11405
Issue