All notable changes to Serde will be documented in this file.
Updates should follow the Keep a CHANGELOG principles.
- Nothing
- Nothing
- A PHP type hint of
DateTimeInterfacewill now deserialize to aDateTimeImmutableobject instead of throwing an error.
- Nothing
- Nothing
- Union, Intersection, and Compound types are now supported. They work by falling back to
mixed, and then relying on the Deformatter to derive the type. Not all Deformatters will have that ability, but the most common bundled ones do. (json,yaml,toml, andarray.) Additionally, Union Types may specifyTypeFields that apply only when specific types are used.
- Version 1.5 and later requires at least PHP 8.2. PHP 8.1 is no longer supported.
- Nothing
- Nothing
- Nothing
- Deserializing to a flattened array property now respects the array type specified by a
SequenceFieldorDictionaryField. That means it is now possible to serialize to/from an array structure, into an object with a single array property. - A new
MixedFieldtype field is available for use onmixedproperties. If specified, it allows specifying a preferred object type that an array-ish value will be cast into when deserializing. If the object deserialization fails, the whole deserialization will fail.
- Nothing
- Serializing an object that is assigned to a
mixedfield will no longer generate a circular reference error.
- The
renameproperty onFieldis nowprivateinstead ofprotected. This shouldn't matter to anyone unless you're extendingField. If you're extendingFieldand messing with therenameproperty, you're probably doing something you shouldn't.
- Nothing
- Nothing
- Nothing
- Default values will now only be extracted from a constructor parameter if it's promoted.
- Switched to PHPDocker.io-based containers for development. (No impact on users.)
- Nothing
- Nothing
- Nothing
- Nothing
- Fixed two implicit nullable arguments for full PHP 8.4 compatibility.
- Nothing
- Nothing
- TOML support! Provided by the
vanodevium/tomllibrary (sold separately). As with YAML, just require that library and Serde will pick it up and use it. Slava Ukraine! - Null values may now be excluded when serializing. See the
omitNullFieldsandomitIfNullflags in the README. - We now require AttributeUtils 1.2, which lets us use closures rather than method name strings for subAttribute callbacks. (Internal improvement.)
- When
strictis false on a sequence or dictionary, numeric strings will get cast to an int or float as appropriate. Previously the list values were processed in strict mode regardless of what the field was set to.
- Nothing
- Greatly simplified and cleaned up the test suite.
- Added better escaping to JSON Stream Formatter to handle strings that contain quotes or other JSON-meaningful characters.
- Fixed handling of deserializing a nullable enum field.
- Nothing
- Nothing
This release includes a small breaking change. The deformatter methods all now have nullable returns. This is necessary to allow for deserializing values that are legitimately and permissibly null. If you do not have any custom Importers, you should not be impacted. If you do have a custom Importer, you may need to adjust your logic to account for the return value from the deformatter being null.
TypeFieldis nowTransitive, so you can implement a custom TypeField for a specific object, and it will apply anywhere it is used.TypeFieldis nowInheritable, too.- There is a new
UnixTimeFieldthat can be applied toDateTime*properties. As it says on the tin, it serializes to/from a Unix timestamp integer, in second, millisecond, or microsecond resolution.
- Nothing
- Explicit null values in incoming data should now deserialize to null-valued properties, assuming the types permit.
- Nothing
- Nothing
The main change in this release is better support for flattening value objects. See the additional section in the README for more details.
- A new
flattenPrefixsetting on flattened fields allows for having multiple properties of the same type that get flattened. The prefix allows them to be differentiated.
- Nothing
serializedName/renameWithis now respected on fields in flattened objects.
- Nothing
- Nothing
- Forgot to include a changelog on 1.0.0, hence 1.0.1. Sigh.
- Include diagrams in the README.
- Split up internal Enums for better type safety.
- Renamed internal Enums for clarity.
- Added a marker interface for all exceptions.
- Null is now a legal value for a property to deserialize to.
- Null values will now be serialized as null, rather than omitted.
- BC BREAK: The return type of formatter methods have changed to support null as a legal value.
arrayTypeon Sequences and Dictionaries can now enforce scalar types.- Serde now uses PHPUnit 10.
- There was a bug that caused default values in attributes to be ignored in some cases. That has been corrected.
- Flattened nullable objects previously got deserialized into empty objects. Now they are left as null.
- Array-based sequences now support non-strict mode, in which they will accept non-sequence arrays but discard the keys.
- In the default SerdeCommon configuration, dictionaries are now checked first, meaning an un-attributed array will get interpreted as a dictionary, not a sequence. This is to minimize data loss. Explicitly specifying a sequence or dictionary attribute is strongly recommended in all cases.
- The sequence and dictionary exporters were eagerly processing lazy properties. This has been corrected, and now a generator property will be serialized one element at a time.
- Support for iterable properties, including generators.
- Support for serializing/deserializing from CSV files.
- Support for stream-serializing to a CSV format.
- Support for specifying a custom format and timezone when serializing DateTime fields.
- Support for making individual fields required when deserializing.
- Support for specifying at the class level that fields are required unless otherwise specified.
- Nothing
- Nothing
- Nothing
- Nothing
- Dictionary fields can now be restricted to just string or just integer keys.
- TypeField definitions now have a validation method to vet values as supportable.
- Nothing
- Dictionary fields now support integer keys by default.
- Nothing
- Nothing