chore(deps): update dependency typo3fluid/fluid to v5 - autoclosed#17
Closed
renovate[bot] wants to merge 1 commit intomainfrom
Closed
chore(deps): update dependency typo3fluid/fluid to v5 - autoclosed#17renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
renovate
bot
force-pushed
the
renovate/typo3fluid-fluid-5.x
branch
10 times, most recently
from
a34c3c7 to
ee8e0b7
Compare
renovate
bot
force-pushed
the
renovate/typo3fluid-fluid-5.x
branch
8 times, most recently
from
6c346c4 to
5d2a063
Compare
renovate
bot
force-pushed
the
renovate/typo3fluid-fluid-5.x
branch
from
5d2a063 to
23de95b
Compare
| datasource | package | from | to | | ---------- | ---------------- | ----- | ----- | | packagist | typo3fluid/fluid | 4.5.1 | 5.1.1 |
renovate
bot
force-pushed
the
renovate/typo3fluid-fluid-5.x
branch
from
23de95b to
f5c0e11
Compare
renovate
bot
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR contains the following updates:
^4.5.1→^5.1.1Release Notes
TYPO3/Fluid (typo3fluid/fluid)
v5.1.1Compare Source
What's Changed
Full Changelog: TYPO3/Fluid@5.1.0...5.1.1
v5.1.0Compare Source
What's Changed
Full Changelog: TYPO3/Fluid@5.0.3...5.1.0
v5.0.3Compare Source
What's Changed
<f:argument>does not work when rendering sections by @cundd in #1274New Contributors
Full Changelog: TYPO3/Fluid@5.0.2...5.0.3
v5.0.2Compare Source
What's Changed
Full Changelog: TYPO3/Fluid@5.0.1...5.0.2
v5.0.1Compare Source
What's Changed
Full Changelog: TYPO3/Fluid@5.0.0...5.0.1
v5.0.0Compare Source
Version 5.0 is the next major milestone in the development of the Fluid templating engine. Based on the previous efforts that went into Fluid 4, Fluid 5 continues to refactor and to modernize the underlining source code, which sometimes requires introducing strategic breaking changes. All breaking changes in this release have been pre-announced in Fluid 4, both in the changelog and by applying the
@deprecatedannotation or emitting a deprecation notice in the code.These breaking changes allow us to ship meaningful new features that weren't possible before:
Streamlined ViewHelper Argument Validation
ViewHelpers now use the
StrictArgumentProcessorto validate ViewHelper arguments. This means that argument validation behaves the same with ViewHelpers and with the<f:argument>ViewHelper, which was introduced with Fluid 4.2. While the new validation might require some adjustments in existing projects, it has clear advantages: ViewHelper instances can actually rely on the types specified in their API to be checked properly by Fluid, which makes a lot of custom validation code obsolete.The new argument validation adds support for union types as well as
iterable,countableandcallable, which allows ViewHelpers to define a clearer API.See #1062, #1074, #1194 and #1226 for more details.
Template File Resolving and File Extension
Fluid 5 now features an internal fallback chain for template file names. Template files are now resolved in the following order (first match wins):
This means that it's no longer necessary for template names to start with an uppercase character. Also, there is a new dedicated file extension
*.fluid.*for Fluid templates:*.fluid.htmlinstead of*.html,*.fluid.xmlinstead of*.xml, and so on. Because of the fallback chain, both can be added without breaking potential overrides from other template paths.We recommend switching to the new file extension if Fluid 5 can be a hard requirement for your project. Otherwise, just stick to the existing general file extensions. The new file extension is entirely optional and will not be a requirement.
See #1243 and #1258 for more details.
Simplified Cache Warmup
Fluid 5 comes with a much simpler way to warmup the template cache in your project. The existing cache warmup functionality has been removed and replaced by a new implementation that requires much less configuration and context. By default, it makes use of the new
*.fluid.*file extension to discover all Fluid templates in your project.See #1224 for more details.
Alternative Syntax for CDATA Sections
A long-standing issue in Fluid templates has been that the Fluid variable and inline ViewHelper syntax collides with inlined CSS or JavaScript code. This issue has now been addressed with Fluid 5: A new alternative syntax has been introduced that makes collisions between CSS/JavaScript and Fluid far less likely.
The normal inline and variable syntax uses single curly braces
{ }as tokens in Fluid templates. In<![CDATA[ ]]>sections, this syntax are now ignored. Instead, three curly braces{{{ }}}can be used to call Fluid ViewHelpers or to access variables. The tag-based syntax is disabled altogether in CDATA sections.See #1246 and the documentation for more details: Avoiding syntax collision with JS and CSS.
Deprecations and Breaking Changes
Please refer to the documentation for a full list of breaking changes and newly introduced deprecations in Fluid 5.0: Changelog 5.x.
What's Changed
Please note that some of the listed changes have been backported to Fluid 4.5.0, most importantly all new ViewHelpers.
ChainedVariableProvider::getby @sascha-egerer in #1165f:maxViewHelper by @eliashaeussler in #1254New Contributors
Full Changelog: TYPO3/Fluid@4.5.0...5.0.0
Configuration
📅 Schedule: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.