Matteo Feltrin
Matteo Feltrin
Waiting for this fix too. With version 2.6.1 our users configurations were based on the concept that a non-required field could be empty, that means not set in the JSON...
After 2 days of digging, it turned out that using eslint.config`.ts` resolved the problem for me. Had also to use the ts parser due to this. Anyway JSDOM is importable...
> > After 2 days of digging, it turned out that using eslint.config`.ts` resolved the problem for me. Had also to use the ts parser due to this. > >...
@zovorap were you able to use stencil rules with Biome?
@dpellier I have understood the problem here, but when you link a @Prop to an element, you are re-rendering it every time, and I think that's not what you want....
Anybody can merge this?
Not sure which is the best way to fix the Psalm error. Should we put another `@template TKey of int` over the $parameters property or should we move the templating...
> The change looks good. Does it apply to lower branches? I'm thinking it would qualify as a forward-compatibility improvement and should therefore go to 2.20 In 2.19 was already...
I have tried to add the templating to `Property Doctrine\ORM\QueryBuilder::$parameters`, the problem is that we have 2 different templates that may not be able to work togheter... My templated property:...
Hmmm, now that you pointed it out I noticed is a problem of PHPStan, not Psalm... When i run it locally I get a slightly different message: ``` Property Doctrine\ORM\QueryBuilder::$parameters...