-
Currently we support built-in serialisation for avro and protobuf.
Avro relies on Confluent.Kafka. Protobuf relies on google.protobuf.
Having serialisation built-in has the following advantages:
…
-
Heya!
Since I borrowed most of the encoding logic for simd-json.rs from just-rust I wanted to contribute back. I improved the write-string logic to use simd instructions to speed up those parts (espe…
-
It's possible to customise JSON serialisation at a global level by changing `JsonConvert.DefaultSettings`, but it would be good to have the option to customise it just for EF Core JSON serialisation b…
-
It would be good to have some standard graph serialisation capacity.
Which would we like to support?
Probably [DOT](http://www.graphviz.org/content/dot-language) at the very least, but I think at le…
-
Hi,
`@Schema` annotation doesn't work while using kotlin serialisation.
(This is due to the fact that this annotation is missing `@SerialInfo` and is removed during serialiser generation.)
I w…
-
I've been looking through external scanners, and was trying to work out how the serialisation worked in this package. Originally, I thought it would try it's best and discard deeper scopes than it cou…
-
Currently we only have Json serialisation. Having binary serialisation should be a bit quicker on load times, and means we don't need to store entities/components as json when packed.
-
We notice that storing qgis date attributes in the dict_properties gives problems when exporting it to geojson (qdate cannot be serialized). Research that this will be handled generic. At the moment t…
-
So we can represent them consistently with validation error
Keats updated
2 years ago
-