Archived

forked from https://github.com/symfony/symfony

This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.

Go to file

Fabien Potencier 5c15496b5c merged branch hason/config_import (PR #6226 ) This PR was merged into the 2.0 branch. Commits ------- `8bb3208` [Config] Loader::import must return imported data Discussion ---------- [2.0][2.1][2.2] [Config] Loader::import must return imported data Bug fix: yes Feature addition: no Backwards compatibility break: no Symfony2 tests pass: yes License of the code: MIT --------------------------------------------------------------------------- by fabpot at 2012-12-07T13:40:58Z why? --------------------------------------------------------------------------- by hason at 2012-12-07T20:57:06Z We should support both approaches to importing. The first case assumes shared object accross all the loaders (loading DI configuration) and the second case requires returning of imported object (merging route collections). --------------------------------------------------------------------------- by stof at 2012-12-07T21:38:42Z @fabpot As ``load`` can have a return value, this PR makes sense IMO --------------------------------------------------------------------------- by fabpot at 2012-12-10T12:44:09Z This change should be done in master then. --------------------------------------------------------------------------- by stof at 2012-12-10T14:43:18Z @fabpot I would consider it as a bugfix. The routing loaders are simply broken (as of 2.0) if the loader does not extend from FileLoader (which overwrites the ``import`` method and takes care to return the value). the routing loaders expect to receive the loaded data when importing instead of loosing the imported data entirely: https://github.com/symfony/Routing/blob/2.0/Loader/XmlFileLoader.php#L80		2012-12-10 15:59:31 +01:00
src/Symfony	[Config] Loader::import must return imported data	2012-12-07 14:24:02 +01:00
tests	[Config] Loader::import must return imported data	2012-12-07 14:24:02 +01:00
.gitignore	add composer to gitignore in 2.0	2012-05-10 16:15:45 +03:00
.travis.yml	Add 5.3.3 to Travis, now is available.	2012-05-28 15:38:15 +03:00
autoload.php.dist	bumped minimal version of Swiftmailer to 4.2.0	2012-06-29 18:02:19 +02:00
CHANGELOG-2.0.md	updated CHANGELOG for 2.0.19	2012-11-29 12:35:10 +01:00
composer.json	Update monolog compatibility	2012-08-19 09:57:44 +02:00
CONTRIBUTING.md	Create CONTRIBUTING.md file for auto-linking in PR's	2012-09-17 14:40:53 -04:00
CONTRIBUTORS.md	update CONTRIBUTORS for 2.0.19	2012-11-29 12:35:34 +01:00
LICENSE	Updated LICENSE files copyright	2012-02-22 10:10:37 +01:00
phpunit.xml.dist	[Locale] fixed tests	2012-12-05 14:13:56 +01:00
README.md	removed the Travis icon (as this is not stable enough -- many false positive, closes #6186 )	2012-12-10 14:50:56 +01:00
UPDATE.ja.md	updated translation of UPDATE file (Japanese RC5 added)	2011-07-30 02:08:25 +09:00
UPDATE.md	UPDATE.md: trivial markdown syntax fix	2011-11-15 10:19:29 -08:00
vendors.php	updated vendors for 2.0.18	2012-10-25 10:54:02 +02:00

README.md

README

What is Symfony2?

Symfony2 is a PHP 5.3 full-stack web framework. It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP.

Symfony can be used to develop all kind of websites, from your personal blog to high traffic ones like Dailymotion or Yahoo! Answers.

Requirements

Symfony2 is only supported on PHP 5.3.2 and up.

Installation

The best way to install Symfony2 is to download the Symfony Standard Edition available at http://symfony.com/download.

Documentation

The "Quick Tour" tutorial gives you a first feeling of the framework. If, like us, you think that Symfony2 can help speed up your development and take the quality of your work to the next level, read the official Symfony2 documentation.

Contributing

Symfony2 is an open source, community-driven project. If you'd like to contribute, please read the Contributing Code part of the documentation. If you're submitting a pull request, please follow the guidelines in the Submitting a Patch section.