flow-development-collection
flow-development-collection copied to clipboard
neos
The unified repository containing the Flow core packages, used for Flow development.
FlowQuery methods are built on magic methods. That is why there is no autocompletion available in IDEs. Available methods are added as doc header which provide autocompletion. **Checklist** - [x]...
This makes sure `guzzlehttp/psr7` is never usd in version with a known security issue. **Checklist** - [x] Code follows the PSR-2 coding style - [x] Tests have been created, run...
### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior When resolving the `Neos\Flow\Validation\Validator\EmailAddressValidator` with options, I get the following exception:...
### Description When settings the `Cache-Control` header, the `ResponseInformationHelper` breaks it in `makeStandardsCompliant` under certain circumstances. ### Steps to Reproduce 1. `$this->response->setHttpHeader('Cache-Control', 'must-revalidate');` #### Expected behavior `Cache-Control: must-revalidate` in response...
### Description The current state about multiline EEL: - it is not possible by the public api to eel / the actual parser may allow it - Fusion will "hack"...
### Description If I run in TypoScript a `find('/sites/shop/products-abc-de/07400/074008468')` I get the following error: ``` The Selector "/sites/shop/products-abc-de/07400/074008468" could not be parsed. Error at character 28 ``` ### Steps to...
Jira issue originally created by user @kitsunet: CollectionInterface is currently pretty useless as it is hard to get Flow to use different implementations than the default one. In ResourceManager::initializeCollections() the...
Jira issue originally created by user @daniellienert: Username is currently "Foo". Login is possible with "foo". Imho Username needs exact match. Created from Forge Issue: https://forge.typo3.org/issues/58733 Jira-URL: https://jira.neos.io/browse/NEOS-458
Before builtin types like `object` or `iterable` in method arguments would lead to being reflected as if they were class types, leading to the AOP proxy builder prefixing those types...
resolves #2665 Allows eel arrow functions to be declared with 0 arguments like in es6: ``` () => 'foo' ``` **What I did** $args will be an empty array. **Checklist**...