Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Avoid and deprecate ParserRuntimeOnly trait #744

Merged
merged 1 commit into from
May 6, 2023
Merged

Conversation

lolli42
Copy link
Member

@lolli42 lolli42 commented May 6, 2023

This trait has been added with 127d8e7 for
no apparent reason: It was used three times
with one consumer overriding the render()
method again. There is no point to have a
trait for methods that only return null
or empty strings.

To simplify the construct a bit, the trait
is avoided and marked as @deprecated. Neither
Flow nor TYPO3 use the trait in own VH's,
impact should be quite small.

This trait has been added with 127d8e7 for
no apparent reason: It was used three times
with one consumer overriding the render()
method again. There is no point to have a
trait for methods that only return null
or empty strings.

To simplify the construct a bit, the trait
is avoided and marked as @deprecated. Neither
Flow nor TYPO3 use the trait in own VH's,
impact should be quite small.
@lolli42 lolli42 merged commit 9ba6bd3 into main May 6, 2023
4 checks passed
@lolli42 lolli42 deleted the lolli-1 branch May 6, 2023 14:59
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.

None yet

2 participants