-
-
Notifications
You must be signed in to change notification settings - Fork 4
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: Migrate fusion context.currentRenderingMode
statements
#28
Conversation
963f7a0
to
54fcabc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new rule should also be added to config/set/contentrepository-90.php
. If think this commented lines could fit:
rector/config/set/contentrepository-90.php
Lines 290 to 292 in 24d8ffc
// ContentContext::getCurrentRenderingMode | |
// TODO: PHP | |
// TODO: Fusion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking care.
Look great, but Anke is right.
Statements accessing `context.currentRenderingMode.edit|preview|name|title|fusionPath|options` on `node|site|documentNode` are migrated. Other uses of `context.currentRenderingMode` are marked with a comment. Resolves: #23
54fcabc
to
e397f70
Compare
Offcourse @ahaeslich is right. Added the line and also adjusted the comments for the other renderingMode rectors. Any suggestions how to adjust this php wise. How can we migrate |
@ahaeslich yes wanted to know wether we could migrate php code aswell |
Statements accessing using
(node|documentNode|site).context.currentRenderingMode.(edit|preview|name|title|fusionPath|options)
are migrated. Other uses ofcontext.currentRenderingMode
are marked with a comment.Resolves: #23