Marc Henry Schultz

@bwaidelich @kitsunet and me agree that it might be time for a new method, or rather a new less static implementation. ------------- _Originally posted by @kitsunet in https://github.com/neos/flow-development-collection/issues/3118#issuecomment-1641510127_ Meh, by...

Also, the static `Scripts` is currently horrible testable: ` TODO: Refactor Scripts class to be more testable.` https://github.com/neos/flow-development-collection/blob/ab1165a6e0863b0f63827faf6cee382216bab025/Neos.Flow/Tests/Unit/Core/Booting/ScriptsTest.php#L26 I now get why you probably shouldn't commit `todos` - because it...

Ha lol, christian tried already once pulling symfony into the game: https://github.com/neos/flow-development-collection/pull/75

Implementing this might make https://github.com/neos/flow-development-collection/issues/2966 easier ^^

This would also allow the `Symfony\Component\Serializer\Normalizer\ObjectNormalizer` to work with proxy classes see https://github.com/neos/neos-development-collection/blob/0976d919a6268f58e05f827793cd78fecd12c1ea/Neos.ContentRepositoryRegistry/Classes/Infrastructure/Property/Normalizer/ProxyAwareObjectNormalizer.php#L12

THanks, i fixed the neos ui problem via https://github.com/neos/neos-ui/commit/d9721fd069b1e9b6745b26fb7006ea1a41912a06

With https://github.com/neos/flow-development-collection/pull/3173 we declared this trait / infrastructure to be fully internal and deprecated. If we find an alternative way to test those two (small) features: https://github.com/neos/flow-development-collection/blob/ad4d67abc9d3e9cef2939968c20e67e6785d326e/Neos.Flow/Tests/Behavior/Features/Security/Policy.method.feature https://github.com/neos/flow-development-collection/blob/ad4d67abc9d3e9cef2939968c20e67e6785d326e/Neos.Flow/Tests/Behavior/Features/Security/Policy.methodWithParameters.feature we can...

maybe it would be a good fit to fix this with 9.0 since its a bit breaking since this behaviour has been now like ever :P Especially the neos ui...

Yes once https://github.com/neos/neos-development-collection/pull/4725 introduces case insensitive operators we might be able to use satisfy the old flow query api? i understand that the new cr subgraph api has different features...

I almost thought this was merged already. Ill will play around with this a bit but then i think (as all the blockers and adjustments were solved) this is ready...