Overview of merged pull requests¶
- Without this annotation it will not be possible to generate doctrine migration.
These classes became useless with the release of 4.0 but were overlooked and forgotten.
PersistentResource no longer provides a
__toString(), so adjust
documentation to that.
We no longer support PhpUnit 4.8 so some code could be removed.
A number of inconsistencies and errors are in the composer manifests of the 4.0 branch:
- some libraries pinned to strictly 4.0.0
- outdated/wrong names and namespaces in merged collection manifest
- inconsistent dependencies on PHP
- inconsistent dependencies on PhpUnit
The first is an actual bug, since even with 4.0.2 of Flow, those packages are pinned to the 4.0.0 version, even though it should be 4.0.2.
While the last two might in fact be correct, the merged manifest is prone to containing wrong constraints, so this change sync the related constraints with the Flow package itself.
$this->typeConverters is not filled during this method, as this method will provide the necessary information, we need to access
$typeConverterMap which contains the class name already.
What I did Fix accessing empty array.
How I did it Accessing method internal existing array containing the necessary information.
How to verify it Register two TypeConverters for same conersion with same priority.
- [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)
I could not find any information about Flow at the given url.
When using the PdoBackend with MySQL for caching, the needed caching tables have to be created manually. This adds a hint on creating the tables to the documentation on the PdoBackend.
Solving the documentation part of neos/flow-development-collection#884
This depends on #886
When not using SQLite for the PdoBackend and manually creating the cache tables by using the DDL.sql, the content column of the cache table with type TEXT could easily lead to cropped caching entries because of the length restriction. Using MEDIUMTEXT practically prevents this issue.
See also: neos/flow-development-collection#884 and neos/flow-development-collection#885
Two small typo 1. doubled «is is» to «it is» 2. doubled «our our» to «our»