packagist jms/serializer-bundle 1.2.0
Expression language support and context factories

latest releases: dev-master, 5.4.0, 5.3.1...
7 years ago

The main news in the v1.2.0 release is the support for features as symfony expression language exclusion strategy and default context factories added in jms serializer v1.4 and v1.5

Implemented enhancements:

Merged pull requests:

Closed issues:

  • All services are broken #541
  • Blank XML breaks XmlDeserializationVisitor error handling #540
  • Customize the serialization of an empty string for XML #538
  • Symfony 3.1 support #533
  • Warning: JMS\Serializer\XmlDeserializationVisitor::visitArray(): Node no longer exists #532
  • Configurable defaults (groups) for serialization #530
  • Setup Problem #525
  • Symfony 3 'json' method gives errors with JMS #523
  • Unable to install with composer :( #520
  • Unable to override default handlers #519
  • Error in security.access.decision_manager service in Symfony 3.1 #518
  • Twig deprecation in Serializer #516
  • Exclude the "discriminator" column for serialized entities #515
  • Installation issues using composer #507
  • PHP7 compatibility #502
  • Float with no decimals are automatically converted to int #497
  • Default context for serialization #495
  • Select attributes in a self referencing field #480
  • The document for yml configuration is confusing, why yml configuration is not working? #477
  • Fix PHP requirements inside composer.json #465
  • Serialize entity with Router dependency #458
  • Enable @expose on code #456
  • Custom handlers on primitive values #455
  • Add server url to image on serialization #451
  • PHP Fatal error: Using $this when not in object context in JMS/Serializer/Serializer.php on line 99 #450
  • Problem with namespace for XMLList #438
  • Discriminator bug fix by upgrading required src #423
  • Exclude based on condition #422
  • When serialized collection of extendend objects returns {/.../} and must be [/../] #418
  • Serialization manyToOne with yml configutaion #411
  • Can I set JSON_FORCE_OBJECT for 1 specific serialization, not for the entire project in config.yml ? #410
  • Fatal error: Invalid opcode 153/1/8 #408
  • if DiExtraBundle not available, JMSSerializer crash #392
  • Wrong Json Response #387
  • custom type using a custom handler for primitives #385
  • Serialize custom properties of entities #377
  • Reflection Exception after upgrade from 0.14.0 to 0.15.0 #369
  • ServiceNotFoundException: You have requested a non-existent service "serializer" #368
  • Question: How can i generate formated response for JSON. #367
  • Include Entity Name in JSON #364
  • serialize_null setting without effect for arrays containing NULL values? #361
  • [Feature request] Relations Serialization Strategy #358
  • Documentation error for installation in AppKernel.php: #354
  • Expected object but got array when serialize ArrayCollection of intermediate entity. #350
  • 0.13 stable tag #344
  • Composer error minimum-stability #330
  • Unexpected extra requests when working with doctrine tree extension. #326
  • Maximum execution time of 30 seconds exceeded #306
  • @Accessor not works in sf2.3 #304
  • Instalation in symfony 2.3 #301
  • Doctrine entity Symfony2 #288
  • serialize_null configuration #287
  • Fatal Error: Cannot redeclare class doctrine\orm\mapping\annotation in /vagrant/vendor/composer/ClassLoader.php line 183 #286
  • Unable to install on Symfony 2.2 #285
  • FatalErrorException: Error: Call to undefined method JMS\Serializer\SerializerBuilder::serialize() #278
  • Add support for wildcard serialization group #269
  • Prevent Doctrine Entities from Serializing #263
  • XML serialization of URLs fail #230
  • custom visitor #218

Don't miss a new serializer-bundle release

NewReleases is sending notifications on new releases.