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 7e2ca4ad93 merged branch jmikola/master-DependencyInjectionExceptions (PR #2786 ) Commits ------- `da0773c` Note DependencyInjection exception changes in the 2.1 changelog `9a090bc` [DependencyInjection] Fix class check and failure message in PhpDumper test `2334596` [DependencyInjection] Use component's SPL classes in dumped service container `3c02ea2` [DependencyInjection] Use exception class for API doc generation `47256ea` [DependencyInjection] Make exceptions consistent when ContainerBuilder is frozen `b7300d2` [DependencyInjection] Fix up @throws documentation `123f514` [DependencyInjection] Use component-specific SPL exceptions `cf2ca9b` [DependencyInjection] Create additional SPL exceptions `ba8322e` [DependencyInjection] Format base exception classes consistently Discussion ---------- [DependencyInjection] Refactor usage of SPL exceptions ``` Bug fix: no Feature addition: no Backwards compatibility break: yes Symfony2 tests pass: yes Fixes the following tickets: - ``` This was something discussed on the mailing list recently and a topic at the last IRC meeting. The DependencyInjection component was what I had in mind while discussing this with @lsmith a few weeks ago, as I found that it already had some local SPL exceptions, which weren't being used directly (only as base classes for the compiler exceptions). This PR replaces uses of core SPL exceptions with the component's equivalents. I've listed it as BC-breaking to be safe, but I don't think it should cause any trouble, since the new exceptions are sub-classes of those originally used. I purposely avoided changing the exceptions in the dumped PHP container. If we agree that's worth doing, it would be a trivial addition to the PR. --------------------------------------------------------------------------- by jmikola at 2011/12/04 22:38:47 -0800 One question I came across while implementing this PR: the doc blocks in ContainerInterface reference InvalidArgumentException (actually the component's local SPL equivalent), but there is no practical need for that class to be used in the file. How will the API doc generator handle this? Do we need to change the doc block reference to the full class path? --------------------------------------------------------------------------- by fabpot at 2011/12/05 01:20:31 -0800 Why have you not replaced the exception in the dumped container code? I don't see any drawback. --------------------------------------------------------------------------- by stof at 2011/12/05 03:39:25 -0800 it would even be better to be consistent in the generated code --------------------------------------------------------------------------- by jmikola at 2011/12/05 09:48:05 -0800 I'll update the exceptions in the dumped container code as well. Thanks for the feedback. --------------------------------------------------------------------------- by jmikola at 2011/12/05 10:41:21 -0800 Ok, this should be ready to review and merge. Tests needed some updating, but they still pass.		2011-12-06 09:42:14 +01:00
src/Symfony	merged branch jmikola/master-DependencyInjectionExceptions (PR #2786 )	2011-12-06 09:42:14 +01:00
tests	merged branch jmikola/master-DependencyInjectionExceptions (PR #2786 )	2011-12-06 09:42:14 +01:00
.gitignore	Added vendor directory to .gitignore	2010-06-24 10:44:28 +02:00
.travis.yml	tweaked travis configuration	2011-11-22 20:12:00 +01:00
autoload.php.dist	fixed autoloader when tests are run on a machine without intl installed	2011-07-20 14:27:10 +02:00
CHANGELOG-2.0.md	updated CHANGELOG for 2.0.6	2011-11-16 20:34:42 +01:00
CHANGELOG-2.1.md	Note DependencyInjection exception changes in the 2.1 changelog	2011-12-05 10:39:21 -08:00
check_cs	fixed root search path to include only './src' and './tests'	2011-06-08 18:11:05 +02:00
composer.json	Adjust composer files to strictly require known to work packages	2011-11-25 15:15:14 +01:00
CONTRIBUTORS.md	update CONTRIBUTORS for 2.0.6	2011-11-16 20:35:23 +01:00
LICENSE	added the LICENSE file for the YAML component	2011-02-18 11:52:11 +01:00
phpunit.xml.dist	[Security] cleaned up opt-in to benchmark test	2011-03-06 20:06:13 +01:00
README.md	set travis-ci icon to master	2011-11-23 11:36:09 +01:00
UPGRADE-2.1.md	Added another "before" possibility to retrieve the locale from a Twig template.	2011-10-22 11:23:43 +02:00
vendors.php	merged 2.0	2011-11-22 10:13:00 +01: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.