neos/flow-development-collection

Flow packages in a joined repository for pull requests.

9.0.0-beta17 2024-12-16 10:21 UTC

Requires

• php: ^8.2
• ext-json: *
• ext-mbstring: *
• ext-reflection: *
• ext-spl: *
• ext-xml: *
• ext-xmlreader: *
• ext-zlib: *
• behat/behat: ^3.10
• composer/composer: ^2.7.7
• doctrine/annotations: ^1.13
• doctrine/common: ^3.1
• doctrine/dbal: ^3.1.4
• doctrine/migrations: ^3.3
• doctrine/orm: ^2.14.0
• egulias/email-validator: ^3.0||^4.0
• guzzlehttp/psr7: ^1.8.4 || ^2.1.1
• laminas/laminas-code: ^4.10
• neos/composer-plugin: ^2.0
• psr/cache: ^2.0 || ^3.0
• psr/container: ^1.0
• psr/http-client: ^1.0
• psr/http-factory: ^1.0
• psr/http-message: ^1.0
• psr/http-server-handler: ^1.0
• psr/http-server-middleware: ^1.0
• psr/log: ^2.0 || ^3.0
• psr/simple-cache: ^2.0 || ^3.0
• ramsey/uuid: ^3.0 || ^4.0
• symfony/console: ^5.1||^6.0
• symfony/dom-crawler: ^5.1||^6.0
• symfony/yaml: ^5.1||^6.0
• typo3fluid/fluid: ^2.8.0

Requires (Dev)

• mikey179/vfsstream: ^1.6.10
• phpunit/phpunit: ~9.1

Suggests

• ext-curl: To use the \Neos\Flow\Http\Client\CurlEngine
• ext-igbinary: The igbinary extension is a replacement for the standard PHP serializer
• ext-memcache: If you have a memcache server and want to use it for caching.
• ext-memcached: Alternative, if you have a memcache server and want to use it for caching.
• ext-redis: If you have a redis server and want to use it for caching.
• doctrine/data-fixtures: To manage and execute the loading of data fixtures for the Doctrine ORM or ODM
• neos/fluid-adaptor: For rendering templates with TYPO3.Fluid
• neos/party: To make use of basic user handling
• php-uuid: For fast generation of UUIDs used in the persistence.

Provides

• psr/cache-implementation: 2.0.0 || 3.0.0
• psr/log-implementation: 2.0.0 || 3.0.0
• psr/simple-cache-implementation: 2.0.0 || 3.0.0

Replaces

• neos/cache: 9.0.0-beta17
• neos/eel: 9.0.0-beta17
• neos/error-messages: 9.0.0-beta17
• neos/flow: 9.0.0-beta17
• neos/flow-log: 9.0.0-beta17
• neos/fluid-adaptor: 9.0.0-beta17
• neos/http-factories: 9.0.0-beta17
• neos/kickstarter: 9.0.0-beta17
• neos/utility-arrays: 9.0.0-beta17
• neos/utility-files: 9.0.0-beta17
• neos/utility-mediatypes: 9.0.0-beta17
• neos/utility-objecthandling: 9.0.0-beta17
• neos/utility-opcodecache: 9.0.0-beta17
• neos/utility-pdo: 9.0.0-beta17
• neos/utility-schema: 9.0.0-beta17
• neos/utility-unicode: 9.0.0-beta17
• symfony/polyfill-mbstring: *
• symfony/polyfill-php70: *
• symfony/polyfill-php71: *
• symfony/polyfill-php72: *
• symfony/polyfill-php73: *
• symfony/polyfill-php74: *
• symfony/polyfill-php80: *

MIT

README

Flow development collection

This repository is a collection of packages for the Flow framework (learn more on http://flow.neos.io/). The repository is used for development and all pull requests should go into it.

If you want to use the Flow framework, please have a look at the documentation: https://flowframework.readthedocs.org/en/latest/

Contributing

If you want to contribute to Flow Framework and want to set up a development environment, then follow these steps:

Clone and install the flow dev distribution https://github.com/neos/flow-development-distribution via git and composer or use this shorthand: composer create-project neos/flow-development-distribution flow-development @dev --keep-vcs

Note the -distribution package you create a project from, instead of just checking out this repository.

The code of the framework can then be found inside Packages/Framework, which itself is the flow-development-collection Git repository (due to the --keep-vcs option above). You commit changes and create pull requests from this repository. To test and commit changes to the framework switch into the Framework directory (cd Packages/Framework).

Here you can do all Git-related work (git add ., git commit, etc).

Unit tests can be run here via ../../bin/phpunit -c ../../Build/BuildEssentials/PhpUnit/UnitTests.xml, functional tests via ../../bin/phpunit -c ../../Build/BuildEssentials/PhpUnit/FunctionalTests.xml and static analysis via composer lint.

To switch the branch you intend to work on run this command in the root of the dev distribution: git checkout 8.3 && composer update

Note

We use an upmerging strategy, so create all bugfixes to lowest maintained branch that

contains the issue (typically the second last LTS release, check the diagram on https://www.neos.io/features/release-process.html), or master for new features.

For more detailed information, see https://discuss.neos.io/t/development-setup/504 and https://discuss.neos.io/t/creating-a-pull-request/506