In order to change the license on this project, we have to get the approval of every past contributor. At the time of writing this we have had 128 contributors.

If you are reading this and you are a contributor on the below list, please reply to this GitHub issue with the following text:

I, @username, agree to license my contributions to the schmittjoh/serializer project from the Apache-2.0 to the MIT license effective immediately.

• [ ] @steveYeah commits code changes, already overwritten in 1.x
• [x] @emgiezet commits changes part of the serializer-bundle already approved in the bundle MIT migration
• [x] @wheelsandcogs commits yaml driver improvements, become part of the bundle repo and already approved in the bundle MIT migration
• [x] @dustin10 commits doc changes, already overwritten in 1.x
• [x] @armetiz
• [x] @JustBlackBird
• [x] @dbu
• [x] @aviortm
• [x] @ftassi
• [x] @helmer
• [x] @lyrixx
• [x] @minayaserrano commits form handling improvements
• [x] @mrosiu
• [x] @Majkl578 commits
• [x] @olvlvl
• [x] @passkey1510
• [x] @ruimarinho
• [x] @l3l0
• [x] @igorw
• [x] @michelsalib
• [x] @toby-griffiths
• [x] @gimler
• [x] @Soullivaneuh
• [x] @0mars
• [x] @dsyph3r
• [x] @ajgarlag
• [x] @emilien-puget
• [x] @scasei
• [x] @TristanMogwai
• [x] @Strate
• [x] @spolischook
• [x] @ribeiropaulor
• [x] @richardfullmer
• [x] @jaymecd
• [x] @cystbear
• [x] @tarjei
• [x] @rande
• [x] @colinfrei
• [x] @Potherca
• [x] @mente
• [x] @DavidMikeSimon
• [x] @Lumbendil
• [x] @wouterj
• [x] @burki
• [x] @rothfahl
• [x] @xanido
• [x] @holtkamp
• [x] @gnat42
• [x] @Nyholm
• [x] @tvlooy
• [x] @rpg600
• [x] @phiamo
• [x] @mikemix
• [x] @hyperized
• [x] @patashnik
• [x] @romantomchak
• [x] @gordalina
• [x] @chasen
• [x] @dunglas
• [x] @greg0ire
• [x] @adrienbrault
• [x] @stof
• [x] @tystr
• [x] @scaytrase
• [x] @xoob
• [x] @jhkchan
• [x] @vicb
• [x] @xabbuh
• [x] @bblue
• [x] @mpajunen
• [x] @hacfi
• [x] @lsmith77
• [x] @yethee
• [x] @anyx
• [x] @jonotron
• [x] @ruudk
• [x] @Aliance
• [x] @robocoder
• [x] @andy-morgan
• [x] @tmilos
• [x] @leonnleite
• [x] @urakozz
• [x] @develth
• [x] @AlexKovalevych
• [x] @smurfy
• [x] @zerkms
• [x] @tyler-sommer
• [x] @bobvandevijver
• [x] @veloxy
• [x] @prosalov
• [x] @goetas
• [x] @schmittjoh
• [x] @chregu
• [x] @alcalyn
• [x] @fdyckhoff
• [x] @megazoll
• [x] @bburnichon
• [x] @akoebbe
• [x] @dragosprotung
• [x] @rosstuck
• [x] @josser
• [x] @Seldaek
• [x] @jockri
• [x] @BraisGabin
• [x] @Bukashk0zzz
• [x] @arghav
• [x] @scrutinizer-auto-fixer (@schmittjoh bot)
• [x] @bertterheide
• [x] @chrisjohnson00
• [x] @jeserkin
• [x] @c0ntax
• [x] @aledeg
• [x] @guilhermeblanco
• [x] @willdurand
• [x] @HarmenM
• [x] @carusogabriel
• [x] @iambrosi
• [x] @zebraf1
• [x] @jgendera
• [x] @enumag
• [x] @kriswallsmith
• [x] @LeaklessGfy
• [x] @marcospassos
• [x] @MDrollette
• [x] @inanimatt
• [x] @JMSBot (@schmittjoh bot)
• [x] @mvanmeerbeck
• [x] @colinmorelli

Things done with this patch:

• Merged #237
• Added documentation for #237
• @XmlNamespace(uri="http://example.com/namespace") acts as default namespace
• XmlDeserializationVisitor
  • Removed a lot of XPath stuff in flavor of simpler SimpleXMLElement::children method
  • Added $objectMetadataStack to access class metadata from a property
• XmlSerializationVisitor
  • Removed unnecessary element prefixing when the document/node default namespace match the desired namesapce
  • Removed some duplicated code, adding createElement and setAttributeOnNode methods

I've tried to implement the XML namespaces support for serialization and deserialization.

Please, review it if you can and tell me what you think about.

Hi, I'm using jms serializer (bundle) in a symfony project. For now, I'm serializing an array of object and it's all ok.

[
{"prop": "value"},
{"prop": "value"},
{"prop": "value"}
]

But I need to add information about the pagination (I fetch data with doctrine) to end up to have a json like this:

[
"meta": {"page": 2, "total": 3, "per_page": 2},
"results": [
   {"prop": "value"},
   {"prop": "value"},
   {"prop": "value"}
   ]
]

As you can see, I need to add the informations about total items, current pagination page and the number of the elements in the page.

I have created a PostSerializationSubscriber that implements JMS\Serializer\EventDispatcher\EventSubscriberInterface and I have implemented the getSubscribedEvents() method like this:

    public static function getSubscribedEvents()
    {
        return [
            [
                'event' => 'serializer.post_serialize',
                'method' => 'onPostSerialize'
            ],
        ];
    }

how can I edit my serialized object in onPostSerialize() method?

    public function onPostSerialize(ObjectEvent $postSerializeEvent)
    {
        $postSerializeEvent->getContext()->getVisitor()->addData('someKey','someValue');
    }

The code below, add 'someKey','someValue' for each elements... but it is not what I want

Thanks

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | | License | MIT

Serializer has trouble with nested objects of polymorphic types; it serializes them as their stated base type in an annotation, rather than their real type.

This PR adds tests which exhibit this bug, then adds an additional pre-serialize event subscriber that corrects the issue.

It doesn't appear that there's a way to give an already constructed object to the deserialize method (in which case the serializer would just skip the object construction phase and begin mapping properties).

My use case is simple: In a REST API, I want to allow a user to create or update objects. Each type of operation (create, update, delete, read) has a different set of security rules. However, with the current implementation of the deserializer (in which we are using the Doctrine object constructor), the user can issue a create request, but specify an "id" as part of the payload. The Doctrine object constructor will then return a mapped entity before deserialization begins, allowing the end user to perform an update (while the server still thinks it's doing a create).

Also, on this point: I was considering making a separate object constructor - but I need to give some attributes to the object constructor on each use (such as the ID which it should construct an object for). Right now, the only way to get those attributes to the deserializer is to include them in the payload string that gets passed to it - which is precisely what I'd like to avoid.

There are ways to handle this in the actual REST endpoint, but none of them are really ideal.What I'd like to be able to do is pass an already-constructed object (which my REST endpoint will handle fetching) to the deserializer and just have it do it's property mapping onto the object. This way, I can always pass a blank object in create calls, while I can pass a constructed object in update calls.

Would this be possible? I could submit a PR if this is something you'd be willing to implement.

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | https://github.com/schmittjoh/serializer/issues/1208 | License | MIT

There are few things worth discussion:

1. What should happen, when incorrect DocBlock type is given?

   /**
   * @var \stdClass
   */
   public array $productIds;
   

Current implementation will throw exception, as above has no sense

2. What should happen, when union type is given?

    /**
    * @var ProductName[]|ProductDescription[]
    */
   public array $productIds;
   

Current implementation will throw exception, as we will not know, which class should be used for deserialization.

3. What should happen, when class does not exists?

    /**
    * @var NotExistingClass[]
    */
   public array $productIds;
   

Current implementation will throw exception as, this class will not be deserializable.

4. If exception is thrown in any case of 1) and 2) 3) what exception type it should be?

Current implementation will throw \InvalidArgumentException

Serializer requires an type attribute to be able to deserialize data when a discriminator map is used. this makes not always sense if the filed only contains a referenced id to an existing object. This option enables to set the strict type checking to true/false on the discriminator map.

Related to https://github.com/schmittjoh/JMSSerializerBundle/issues/292

Hello The actual DateHandler support DateTime and DateInterval types. Would you consider adding DateTimeImmutable support for this handler ? I can do a Pr if you like the idea.

Regards,

@mathroc

I have a strange Problem here,

im getting this Error on serialization:

[LogicException]
The sub-class "Dl\DomainModel\Proxies\__CG__\Dl\Component\DomainModel\Product\Attribute\EntityAttribute" is not listed in the discriminator of the base class "Dl\Component\DomainModel\Product\Attribute\AbstractAttribute".

it happens during serialization:

 [file]: string (57) "/www/vendor/jms/metadata/src/Metadata/MetadataFactory.php"
 [line]: int 150
 [function]: string (5) "merge"
 [class]: string (37) "JMS\Serializer\Metadata\ClassMetadata"
 [type]: string (2) "->"
 [args]: array (1)
  · [0]: object(JMS\Serializer\Metadata\ClassMetadata)

 [1]: array (6)
 [file]: string (57) "/www/vendor/jms/metadata/src/Metadata/MetadataFactory.php"
 [line]: int 105
 [function]: string (16) "addClassMetadata"
 [class]: string (24) "Metadata\MetadataFactory"
 [type]: string (2) "->"
 [args]: array (2)
  · [0]: object(JMS\Serializer\Metadata\ClassMetadata)
  · [1]: object(JMS\Serializer\Metadata\ClassMetadata)

 [2]: array (6)
 [file]: string (64) "/www/vendor/jms/serializer/src/JMS/Serializer/GraphNavigator.php"
 [line]: int 188
 [function]: string (19) "getMetadataForClass"
 [class]: string (24) "Metadata\MetadataFactory"
 [type]: string (2) "->"
 [args]: array (1)
  · [0]: string (88) "Dl\DomainModel\Proxies\__CG__\Dl\Component\DomainModel\Product\Attribute\EntityAttribute"

 [3]: array (6)
 [file]: string (77) "/www/vendor/jms/serializer/src/JMS/Serializer/GenericSerializationVisitor.php"
 [line]: int 140
 [function]: string (6) "accept"
 [class]: string (29) "JMS\Serializer\GraphNavigator"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(Dl\DomainModel\Proxies\__CG__\Dl\Component\DomainModel\Product\Attribute\EntityAttribute)
  · [1]: array (2)
  ·  · [name]: string (88) "Dl\DomainModel\Proxies\__CG__\Dl\Component\DomainModel\Product\Attribute\EntityAttribute"
  ·  · [params]: array (0)

  · [2]: object(JMS\Serializer\SerializationContext)

 [4]: array (6)
 [file]: string (64) "/www/vendor/jms/serializer/src/JMS/Serializer/GraphNavigator.php"
 [line]: int 235
 [function]: string (13) "visitProperty"
 [class]: string (42) "JMS\Serializer\GenericSerializationVisitor"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(JMS\Serializer\Metadata\PropertyMetadata)
  · [1]: object(Dl\Component\DomainModel\Partner\UnmatchedValue)
  · [2]: object(JMS\Serializer\SerializationContext)

 [5]: array (6)
 [file]: string (77) "/www/vendor/jms/serializer/src/JMS/Serializer/GenericSerializationVisitor.php"
 [line]: int 102
 [function]: string (6) "accept"
 [class]: string (29) "JMS\Serializer\GraphNavigator"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(Dl\Component\DomainModel\Partner\UnmatchedValue)
  · [1]: array (2)
  ·  · [name]: string (47) "Dl\Component\DomainModel\Partner\UnmatchedValue"
  ·  · [params]: array (0)

  · [2]: object(JMS\Serializer\SerializationContext)

 [6]: array (6)
 [file]: string (74) "/www/vendor/jms/serializer/src/JMS/Serializer/JsonSerializationVisitor.php"
 [line]: int 55
 [function]: string (10) "visitArray"
 [class]: string (42) "JMS\Serializer\GenericSerializationVisitor"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(Dl\Component\Helpers\DataType\ArrayCollection)
  · [1]: array (2)
  ·  · [name]: string (5) "array"
  ·  · [params]: array (1)
  ·  ·  · [0]: array (2)
  ·  ·  ·  · [name]: string (47) "Dl\Component\DomainModel\Partner\UnmatchedValue"
  ·  ·  ·  · [params]: array (0)

  · [2]: object(JMS\Serializer\SerializationContext)

 [7]: array (6)
 [file]: string (64) "/www/vendor/jms/serializer/src/JMS/Serializer/GraphNavigator.php"
 [line]: int 129
 [function]: string (10) "visitArray"
 [class]: string (39) "JMS\Serializer\JsonSerializationVisitor"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(Dl\Component\Helpers\DataType\ArrayCollection)
  · [1]: array (2)
  ·  · [name]: string (5) "array"
  ·  · [params]: array (1)
  ·  ·  · [0]: array (2)
  ·  ·  ·  · [name]: string (47) "Dl\Component\DomainModel\Partner\UnmatchedValue"
  ·  ·  ·  · [params]: array (0)

  · [2]: object(JMS\Serializer\SerializationContext)

 [8]: array (6)
 [file]: string (77) "/www/vendor/jms/serializer/src/JMS/Serializer/GenericSerializationVisitor.php"
 [line]: int 140
 [function]: string (6) "accept"
 [class]: string (29) "JMS\Serializer\GraphNavigator"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(Dl\Component\Helpers\DataType\ArrayCollection)
  · [1]: array (2)
  ·  · [name]: string (5) "array"
  ·  · [params]: array (1)
  ·  ·  · [0]: array (2)
  ·  ·  ·  · [name]: string (47) "Dl\Component\DomainModel\Partner\UnmatchedValue"
  ·  ·  ·  · [params]: array (0)

  · [2]: object(JMS\Serializer\SerializationContext)

 [9]: array (6)
 [file]: string (64) "/www/vendor/jms/serializer/src/JMS/Serializer/GraphNavigator.php"
 [line]: int 235
 [function]: string (13) "visitProperty"
 [class]: string (42) "JMS\Serializer\GenericSerializationVisitor"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(JMS\Serializer\Metadata\PropertyMetadata)
  · [1]: object(Dl\Import\Task\PersistTask)
  · [2]: object(JMS\Serializer\SerializationContext)

 [10]: array (6)
 [file]: string (60) "/www/vendor/jms/serializer/src/JMS/Serializer/Serializer.php"
 [line]: int 176
 [function]: string (6) "accept"
 [class]: string (29) "JMS\Serializer\GraphNavigator"
 [type]: string (2) "->"
 [args]: array (3)
  · [0]: object(Dl\Import\Task\PersistTask)
  · [1]: array (2)
  ·  · [name]: string (26) "Dl\Import\Task\PersistTask"
  ·  · [params]: array (0)

  · [2]: object(JMS\Serializer\SerializationContext)

 [11]: array (6)
 [file]: string (60) "/www/vendor/jms/serializer/src/JMS/Serializer/Serializer.php"
 [line]: int 82
 [function]: string (5) "visit"
 [class]: string (25) "JMS\Serializer\Serializer"
 [type]: string (2) "->"
 [args]: array (4)
  · [0]: object(JMS\Serializer\JsonSerializationVisitor)
  · [1]: object(JMS\Serializer\SerializationContext)
  · [2]: object(Dl\Import\Task\PersistTask)
  · [3]: string (4) "json"

 [12]: array (2)
 [function]: string (44) "Closure$JMS\Serializer\Serializer::serialize"
 [args]: array (1)
  · [0]: object(JMS\Serializer\JsonSerializationVisitor)

 [13]: array (4)
 [file]: string (54) "/www/vendor/phpoption/phpoption/src/PhpOption/Some.php"
 [line]: int 89
 [function]: string (14) "call_user_func"
 [args]: array (2)
  · [0]: object(Closure$JMS\Serializer\Serializer::serialize;1748757503)
  · [1]: object(JMS\Serializer\JsonSerializationVisitor)

 [14]: array (6)
 [file]: string (60) "/www/vendor/jms/serializer/src/JMS/Serializer/Serializer.php"
 [line]: int 85
 [function]: string (3) "map"
 [class]: string (14) "PhpOption\Some"
 [type]: string (2) "->"
 [args]: array (1)
  · [0]: object(Closure$JMS\Serializer\Serializer::serialize;1748757503)

anyone have a clue why this occurs?

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | N/A | License | MIT

This will allow using the doctrine/annotations package's 2.x release with the serializer. The only B/C issue in https://github.com/doctrine/annotations/blob/2.0.x/UPGRADE.md that looks to impact this package was already addressed by #1447 so there shouldn't be any other problems.

This PR handles constructor property promotion for docblock type resolver.

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | | License | MIT

This PR provides possibility to serialize and deserialize phpstan array shapes.

As no matter of the structure JMS can handle arrays, instead of throwing exception when we meet phpstan array shape, we can simply serialize it as array.

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | | License | MIT

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | yes | BC breaks? | maybe?? | Deprecations? | no | Tests pass? | yes | Fixed tickets | #1393 #1392 #1373 | License | MIT

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Doc updated | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | | License | MIT

Bump code style to PHPStan lvl 2. Improved types whenever it was possible. Enabled only for PHP8.1. PHP 8.0 and PHP 7.4 still uses lvl 1.

| Q | A | ------------- | --- | Bug fix? |no | New feature? |no | Doc updated | yes | BC breaks? |no | Deprecations? |no | Tests pass? | yes | License | MIT