fluid-plugin issues
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues
2024-01-25T13:44:35Z
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/201
Add an auto completion to the form view helper
2024-01-25T13:44:35Z
Fabian Galinski
Add an auto completion to the form view helper
Auto completion for all attributes
Go-To functions for these
Line markers
Auto completion for all attributes
Go-To functions for these
Line markers
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/200
Add an auto completion to the action view helper
2024-01-25T13:44:11Z
Fabian Galinski
Add an auto completion to the action view helper
Auto completion for all attributes
Go-To functions for these
Line markers
Auto completion for all attributes
Go-To functions for these
Line markers
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/196
Feature: fluid-tags in an other color than html-tags
2023-12-21T02:59:18Z
Fabian Galinski
Feature: fluid-tags in an other color than html-tags
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...
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/186
Allow ViewHelpers from libraries
2023-06-19T10:57:38Z
Stefan Galinski
stefan@sgalinski.de
Allow ViewHelpers from libraries
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 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/183
Bug: Convert Tag to Inline
2024-01-04T14:24:38Z
Ingo Fabbri
Bug: Convert Tag to Inline
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/...
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/173
Proper rendering of f:asset.script and f:asset.css
2023-05-11T18:22:40Z
Stefan Galinski
stefan@sgalinski.de
Proper rendering of f:asset.script and f:asset.css
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.
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/161
Support Fluid components
2022-03-29T18:15:00Z
Ingo Fabbri
Support Fluid components
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.
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/144
[FEATURE] Synchronize License with JetBrains Profile / IDE Settings Sync Service
2020-05-29T11:15:56Z
Armin Linzbauer
2424-arminlinzbauer@users.noreply.gitlab.sgalinski.de
[FEATURE] Synchronize License with JetBrains Profile / IDE Settings Sync Service
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 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/142
Autocompletion of short notation inside html tag.
2020-10-22T22:02:10Z
Mr660
Autocompletion 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/140
Prevent duplicate code from being marked if only one can ever be rendered
2020-10-22T22:02:38Z
Tim Wagner
Prevent duplicate code from being marked if only one can ever be rendered
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 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/118
Implementation for LightCodeInsights-Tests
2018-10-05T14:43:53Z
Fabian Galinski
Implementation for LightCodeInsights-Tests
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/115
Change the Fluid annotations to the new system like for the comments.
2018-08-30T14:04:48Z
Fabian Galinski
Change the Fluid annotations to the new system like for the comments.
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/113
Implement arrays and objects to the controller variables auto completion
2018-08-24T11:05:40Z
Fabian Galinski
Implement arrays and objects to the controller variables auto completion
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/111
Recognize the defined variables in a f:alias, f:for and similiar view helpers...
2018-08-22T11:02:27Z
Fabian Galinski
Recognize the defined variables in a f:alias, f:for and similiar view helpers. Note: There is a function which needs to be respected
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/110
Auto Completion of variables for partials
2018-08-22T10:28:47Z
Fabian Galinski
Auto Completion of variables for partials
Logic:
1. Check where the partial is used
2. Check the argument "arguments" for variables
3. Allow these variables in the auto completion
Logic:
1. Check where the partial is used
2. Check the argument "arguments" for variables
3. Allow these variables in the auto completion
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/93
QuickSwitch from Controller to Template and Back
2017-07-16T19:15:23Z
Stefan Galinski
stefan@sgalinski.de
QuickSwitch from Controller to Template and Back
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/90
Fluid inline notation: Namespace declaration is never used
2018-08-22T10:17:30Z
Ghost User
Fluid inline notation: Namespace declaration is never used
If a fluid namespace is only used in inline notations (https://wiki.typo3.org/Fluid_Inline_Notation) PHPStorm can't detect the usage. So it outputs the warning "Namespace declaration is never used":
http://imgur.com/a/MGryB
It would be ...
If a fluid namespace is only used in inline notations (https://wiki.typo3.org/Fluid_Inline_Notation) PHPStorm can't detect the usage. So it outputs the warning "Namespace declaration is never used":
http://imgur.com/a/MGryB
It would be nice if the fluid plugin could tell PHPStorm, that the namespace is used.
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/52
Generators for XMLNS namespaces
2020-05-25T21:07:21Z
Fabian Galinski
Generators for XMLNS namespaces
required: #51
Possible Generators:
- Converting the old implementation to the new one
- Adding the namespaces on all Templates/Partials/Layouts
required: #51
Possible Generators:
- Converting the old implementation to the new one
- Adding the namespaces on all Templates/Partials/Layouts
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/40
Autocompletion for Variables defined with FluidDoc
2022-08-18T09:15:55Z
René Maas
Autocompletion for Variables defined with FluidDoc
Would be nice to have autocompletion for Fluid-Doc defined variables:
<f:comment>
// @var {\Vendor\Extension\Domain\Model\Seminar} seminar
</f:comment>
{seminar.<autocompletion for properties defined in mode...
Would be nice to have autocompletion for Fluid-Doc defined variables:
<f:comment>
// @var {\Vendor\Extension\Domain\Model\Seminar} seminar
</f:comment>
{seminar.<autocompletion for properties defined in model>}
https://gitlab.sgalinski.de/phpstorm/fluid-plugin/-/issues/29
Jump to more file types
2017-08-11T14:44:59Z
Markus Guenther
Jump to more file types
It would be nice if the fluid plugin understands more file types for jumps.
For instance:
```
<f:translate key="frontend.common.foo" arguments="{0: '{foo}'}" />
<f:uri.resource path="StyleSheets/FooBar.css" />
```
With the flui...
It would be nice if the fluid plugin understands more file types for jumps.
For instance:
```
<f:translate key="frontend.common.foo" arguments="{0: '{foo}'}" />
<f:uri.resource path="StyleSheets/FooBar.css" />
```
With the fluid conventions we actually know where the resources are and can jump directly to the CSS file or to the default language file.