Skip to content

2.10.0 (2015-10-23)
Compare
Choose a tag to compare
@willdurand willdurand released this 23 Oct 09:43
· 1018 commits to master since this release
2.10.0
fb86395
This commit was signed with the committer’s verified signature. The key has expired.
willdurand William Durand
GPG key ID: A509BCF1C1274F3B
Expired
Learn about vigilant mode.

Hi!

(Please read the text below, thanks!)

This release contains numerous fixes and a few improvements. Most of them are related to newer versions of different dependencies. For instance, this bundle now requires Symfony 2.3+ (it does not work well with 2.8|3.0 though). Take a look at the CHANGELOG section at the end of this page for more information. Thank you to all contributors!

The "Pull-Request-Gate"

I refactored the test suite a bit in order to speed it up, nothing fancy here but the feedback loop gets better. Talking about it, I am alone maintaining this bundle I've created more than 3 years ago. However, I don't have the opportunity to use it anymore, so it is rather complicated to check Pull Requests and to fix bugs. It took me some time to understand why the test suite was failing for weeks.

Now that it is back to green, I decided to close all open PRs, because CI statuses are "stale" (i.e. statuses don't reflect the real statuses of the PRs). It does not mean that I won't accept PRs anymore, but it is time to start from scratch. That is why all PRs are now closed. I hope you will better understand why I did that now (note also that I closed all PRs using the GitHub interface, that is why I didn't leave any message...).

Roadmap Proposal

Anyway, v2.10 should be pretty stable (most of the other versions were stable) and should work well with all stable Symfony versions. What I'd like to do first is:

  1. make the bundle stable = make it work well with all Symfony versions > 2.3. There is some work for the upcoming Symfony versions (> 2.7). I think it should be easy, but I need your help.
  2. fix the integration of the DunglasApiBundle. This feature introduced in a previous version is not stable enough, due to recent changes. It is an optional dependency and feature, so it should not impact many users, but it would be nice to have a good integration of this bundle, because it deserves it :)
  3. accept new features/improvements again

One More Thing

I will continue to maintain this bundle, to fix bugs, and to merge new features. This bundle has been installed more than 2 million times. 2 million. That's a lot, and it is constantly increasing (according to Packagist), which means this bundle is more and more used. Behind these numbers, there are developers just like you and me. If you use this bundle, and want to give it some love like these 100 awesome developers already, please contribute!

You can ping me on Twitter if you want to talk to me.

Thank you,
William.

CHANGELOG

  • Warning: bump Symfony requirements to 2.3
  • Warning: switched to stable version of DunglasApiBundle
  • Added: Twig 2 compatibility
  • Added: a parser for JsonSerializable classes
  • Added: support for using name in the input and output options for JsonSerializable and validation parsers
  • Added: pipe to escaped symbols of jQuery selector
  • Added: handle "array" parameter in FOSRestBundle QueryParam or RequestParam
  • Added: improve true/false/null default values on configuration
  • Added: view option to api:doc:dump command
  • Fixed: deprecated route options
  • Fixed: mistake in #720
  • Fixed: deprecated twig stuff usage
  • Fixed: ApiDocExtractor to accept callable classes as controllers
  • Fixed: prevent BC break in DunglasApiBundle
  • Fixed: change getViewCache() method visibility to private
  • Fixed: extractor view data caching
  • Fixed: prevent error "Undefined index" when no subtype provided
  • Fixed: only display filters on collections GET services
  • Fixed: deprecated FormType::setDefaultOptions() usage
  • Fixed: reverted fix "LINK workaround for firefox"
Assets 2
Loading