Symfony2: How to create framework independent controllers? — Matthias Noback - Blog
Part I: Don't use the standard controller The general belief is that controllers are the most tightly coupled classes in every application. Most of the time based on the request data, they fetch and/or store persistent data from/in some place, then turn the data into HTML, which serves as the response to the client who initially made the request. So controllers are "all over the place", they glue
Symfony2: Creating a Validator with dependencies? Make it a service! — Matthias Noback - Blog
One of the ugly things about Symfony 1 validators was that their dependencies were generally fetched from far away, mainly by calling sfContext::getInstance(). With Symfony2 and it's service container, this isn't necessary anymore. Validators can be services. The example below is quite simple, but given you can inject anything you want, you can make it quite complicated. I show you how to create a
Symfony2: Setting up a Console-centered Application (with Composer) — Matthias Noback - Blog
I recently took a quick look at Composer and I have come to like it very much. I want to demonstrate the incredible ease of use. My example is also not trivial, it means to elaborate on the concept of a Console Application. The Symfony2 documentation does not tell us how to use the Console Component stand-alone, but only shows us how to add new commands to an already existing application. Therefor
Symfony2 & TDD: Testing a Configuration Class — Matthias Noback - Blog
Some of you may already know: I am a big fan of TDD - the real TDD, where you start with a failing test, and only write production code to make that specific test pass (there are three rules concerning this actually). The TDD approach usually works pretty well for most classes in a project. But there are also classes which are somewhat difficult to test, like your bundle's extension class, or its
Symfony2 & JMSSerializerBundle: Vendor MIME types and API versioning — Matthias Noback - Blog
The JMSSerializerBundle has a VersionExclusionStrategy, which allows you to serialize/deserialize objects for a specific version of your API. You can mark the properties that are available for different versions using the @Since and @Until annotations: use JMS\SerializerBundle\Annotation\Type; use JMS\SerializerBundle\Annotation\Since; use JMS\SerializerBundle\Annotation\Until; class Comment { /**
Symfony2: running PHPUnit from within a controller — Matthias Noback - Blog
This article is deprecated. I don't think it's a good idea to run your unit tests in a controller. When you don't have access to the command-line of your webserver, it may be nice to still run all your unit tests; so you need a way to execute the phpunit command from within a controller. This way, you can call your test suite by browsing to a URL of your site. To do things right, we start with a "
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Inject the ManagerRegistry instead of the EntityManager — Matthias Noback - Blog
Why Symfony? Seven Facts — Matthias Noback - Blog
Symfony2: Rich Console Command Output Using AOP — Matthias Noback - Blog