fluid-plugin issueshttps://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues2020-10-22T22:02:38Zhttps://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/140Prevent duplicate code from being marked if only one can ever be rendered2020-10-22T22:02:38ZTim WagnerPrevent duplicate code from being marked if only one can ever be renderedPhpStorm detects and marks duplicate code fragments, such as IDs in HTML.
In some cases, only one may appear in the rendered HTML, for example if they are in the `<f:then>` and the `<f:else>` blocks of an `<f:if>` statement. In this cas...PhpStorm detects and marks duplicate code fragments, such as IDs in HTML.
In some cases, only one may appear in the rendered HTML, for example if they are in the `<f:then>` and the `<f:else>` blocks of an `<f:if>` statement. In this case, there will never be a duplicate ID in the frontend.
Here is an example of such a code block:
![image](/uploads/0b5712139b9e40a0f7dad0ee53fbd9ca/image.png)https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/142Autocompletion of short notation inside html tag.2020-10-22T22:02:10ZMr660Autocompletion of short notation inside html tag.Phpsotrm doesn't allow short notation fluid inside html tag. It works outside tags and inside attributes but not inside html tag. Without it we can't do such a simple thing like conditionally displaying some tag. Not having such a simple...Phpsotrm doesn't allow short notation fluid inside html tag. It works outside tags and inside attributes but not inside html tag. Without it we can't do such a simple thing like conditionally displaying some tag. Not having such a simple thing ofenly makes templates look really awfull and it forces us to always have empty tag when it's totally not needed.!
[image](/uploads/c1902650bc85a13414bda180968f8eb1/image.png)https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/144[FEATURE] Synchronize License with JetBrains Profile / IDE Settings Sync Service2020-05-29T11:15:56ZArmin Linzbauer2424-arminlinzbauer@users.noreply.gitlab.sgalinski.de[FEATURE] Synchronize License with JetBrains Profile / IDE Settings Sync ServiceI would really like to have my plugin license(s) synchronized with my JetBrains profile / the IDE's Settings Synchronization Service so I won't have to enter it again after every IDE update. If that isn't at all possible please let me kn...I would really like to have my plugin license(s) synchronized with my JetBrains profile / the IDE's Settings Synchronization Service so I won't have to enter it again after every IDE update. If that isn't at all possible please let me know! This also applies to the TypoScript plugin.https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/161Support Fluid components2022-03-29T18:15:00ZIngo FabbriSupport Fluid componentsPlease (re-)add support for https://extensions.typo3.org/extension/fluid_components
It worked a while ago, but components are not recognized anymore.
I guess you need additional context. I'll try to answer and give feedback.Please (re-)add support for https://extensions.typo3.org/extension/fluid_components
It worked a while ago, but components are not recognized anymore.
I guess you need additional context. I'll try to answer and give feedback.https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/173Proper rendering of f:asset.script and f:asset.css2023-05-11T18:22:40ZStefan Galinskistefan@sgalinski.deProper rendering of f:asset.script and f:asset.cssIt would be great if the content (JavaScript/CSS) is displayed correctly in PhpStorm between the tags: f:asset.script and f:asset.css - i.e. with indentation/color.It would be great if the content (JavaScript/CSS) is displayed correctly in PhpStorm between the tags: f:asset.script and f:asset.css - i.e. with indentation/color.https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/183Bug: Convert Tag to Inline2024-01-04T14:24:38ZIngo FabbriBug: Convert Tag to InlineDoesn't quite work well. Seems like this "conversion" is not aware of tag content/children.
![image](/uploads/2cb6fd73ce5683cbb3f761e5d98d5f0f/image.png)
![image](/uploads/925fad8acb465203e5f988e83599a373/image.png)
![image](/uploads/...Doesn't quite work well. Seems like this "conversion" is not aware of tag content/children.
![image](/uploads/2cb6fd73ce5683cbb3f761e5d98d5f0f/image.png)
![image](/uploads/925fad8acb465203e5f988e83599a373/image.png)
![image](/uploads/fc76c2b258dddea08ef1e6783f42c9c9/image.png)
---
![image](/uploads/95c15747e91f81b34c6df4a1946d05dd/image.png)
![image](/uploads/dbc403c7f12ddfccc0403fce9860a384/image.png)https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/186Allow ViewHelpers from libraries2023-06-19T10:57:38ZStefan Galinskistefan@sgalinski.deAllow ViewHelpers from librarieshttps://review.typo3.org/c/Packages/TYPO3.CMS/+/79175
With TYPO3 11 it was possible to use ViewHelpers from composer libraries
that aren't TYPO3 extensions and thus don't use Symfony dependency
injection. With the removal of objectManag...https://review.typo3.org/c/Packages/TYPO3.CMS/+/79175
With TYPO3 11 it was possible to use ViewHelpers from composer libraries
that aren't TYPO3 extensions and thus don't use Symfony dependency
injection. With the removal of objectManager, this doesn't work anymore
in TYPO3 12 because the dependency injection can only instantiate
ViewHelper classes that are defined as public services explicitly.
This change reintroduces that functionality by falling back to "new" if
the class exists but isn't registered as a service. Fluid standalone
uses the same method to instantiate a ViewHelper.https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/196Feature: fluid-tags in an other color than html-tags2023-12-21T02:59:18ZFabian GalinskiFeature: fluid-tags in an other color than html-tagsSince TYPO3 v11, the plugin is not working anymore (even with composer-installers v3). Furthermore, in upcoming versions of TYPO3, the extension dirs won't have the typical structure `typo3conf/ext` or `typo3/sysext`. Most of my projects...Since TYPO3 v11, the plugin is not working anymore (even with composer-installers v3). Furthermore, in upcoming versions of TYPO3, the extension dirs won't have the typical structure `typo3conf/ext` or `typo3/sysext`. Most of my projects are already v11, in some of them I'm already using the v4-RC of `typo3/cms-composer-installers`. We really miss the comfort of this plugin! Let me know if there are any plans for updates - or if you need a sponsor.https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/200Add an auto completion to the action view helper2024-01-25T13:44:11ZFabian GalinskiAdd an auto completion to the action view helperAuto completion for all attributes
Go-To functions for these
Line markersAuto completion for all attributes
Go-To functions for these
Line markershttps://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/201Add an auto completion to the form view helper2024-01-25T13:44:35ZFabian GalinskiAdd an auto completion to the form view helperAuto completion for all attributes
Go-To functions for these
Line markersAuto completion for all attributes
Go-To functions for these
Line markers