Overview of merged pull requests¶
Extended CurlEngine for request-type HEAD to set the option to not expect a body.
This improves the error message on missing AOP runtime expressions just a little.
Trait introduction is available since some time, but it was never documented. This change adds a short explanation with a code example to fix that.
Without this change a package (defined by composer name eg. “neos/party”) that exists two times in the installation would be silently ignored and added with the second path found. This could still result in strange effects happening as autoload and Flow internal paths (configuration, resources) could diverge.
With this change an exception is thrown when the package states are resolved and a package is found a second time.
When introducing a trait using AOP it now works if the class only has traits introduced via AOP.
unpublishFile() in the FileSystemTarget does not remove symlinks correctly, thus the method is adjusted in the FileSystemSymlinkTarget to check using is_link() instead of file_exists().
Changes some package names used in a test and a comment in a class to no longer mention TYPO3, TypoScript or TYPO3CR.
Have Add a note to chapter «Installation» and change the sequence in chaper «Configuration» for better usable/find the context-part, not to skip because of note I moved this to the end and add more subtitle about context for better SERP-Result.
More Details about the reason in slack-channel «guilde-documentation»
(Second try: Sorry)
The test would create a Flow package in the current installation as the package manager in the test was not prepared with a virtual filesystem.
Previously the route parts were evaluated correct regardless of the configured keys because the schema used the configuration additionalAttributes = FALSE instead of additionalProperties = FALSE. This is fixed and the schema is updated
- validate the keys in route parts strictly
- allow configuration of objectType and uriPattern ` instead of `handler
- allow options and toLowerCase for all routeParts
- [x] Code follows the PSR-2 coding style
- [ ] Tests have been created, run and adjusted as needed
- [x] The PR is created against the [lowest maintained branch](https://www.neos.io/features/release-roadmap.html)
Custom configuration types of processing type settings could break the compile process as the array wouldn’t have the custom configuration name as key set because it was never initialized in this processing type.
This change initializes any configuration type with an empty array in the beginning and provides a test to proof the behavior.