platform/README.md

212 lines
6 KiB
Markdown
Raw Normal View History

2017-06-16 19:47:13 +00:00
# serialize
2017-06-17 01:56:38 +00:00
[![Pub](https://img.shields.io/pub/v/angel_serialize.svg)](https://pub.dartlang.org/packages/angel_serialize)
[![build status](https://travis-ci.org/angel-dart/serialize.svg)](https://travis-ci.org/angel-dart/serialize)
2017-07-10 15:15:09 +00:00
Source-generated serialization for Dart objects. This package uses `package:source_gen` to eliminate
2017-06-17 01:56:38 +00:00
the time you spend writing boilerplate serialization code for your models.
2017-07-10 15:15:09 +00:00
`package:angel_serialize` also powers `package:angel_orm`.
2017-06-17 01:56:38 +00:00
* [Usage](#usage)
* [Models](#models)
2018-03-02 18:48:03 +00:00
* [Field Aliases](#aliases)
* [Excluding Keys](#excluding-keys)
2018-03-02 18:55:03 +00:00
* [Serialization](#serializaition)
2017-06-17 01:56:38 +00:00
* [Nesting](#nesting)
2018-03-02 18:48:03 +00:00
* [ID and Date Fields](#id-and-dates)
2017-06-17 01:56:38 +00:00
# Usage
2017-07-10 15:15:09 +00:00
In your `pubspec.yaml`, you need to install the following dependencies:
2017-06-17 01:56:38 +00:00
```yaml
dependencies:
2018-03-02 21:23:00 +00:00
angel_serialize: ^2.0.0
2017-06-17 01:56:38 +00:00
dev_dependencies:
2018-03-02 21:23:00 +00:00
angel_serialize_generator: ^2.0.0
2018-03-02 18:48:03 +00:00
build_runner: ^0.7.0
2017-06-17 01:56:38 +00:00
```
2018-03-02 21:23:00 +00:00
With the recent updates to `package:build_runner`, you can build models in
`lib/src/models/**.dart` automatically by running `pub run build_runner build`.
2017-06-17 01:56:38 +00:00
2018-03-02 21:23:00 +00:00
To tweak this:
https://pub.dartlang.org/packages/build_config
2017-06-17 01:56:38 +00:00
If you want to watch for file changes and re-build when necessary, replace the `build` call
with a call to `watch`. They take the same parameters.
# Models
There are a few changes opposed to normal Model classes. You need to add a `@serializable` annotation to your model
class to have it serialized, and a serializable model class's name should also start
with a leading underscore. In addition, you may consider using an `abstract` class.
Rather you writing the public class, `angel_serialize` does it for you. This means that the main class can have
its constructors automatically generated, in addition into serialization functions.
For example, say we have a `Book` model. Create a class named `_Book`:
```dart
library angel_serialize.test.models.book;
import 'package:angel_framework/common.dart';
import 'package:angel_serialize/angel_serialize.dart';
part 'book.g.dart';
@serializable
abstract class _Book extends Model {
String author, title, description;
int pageCount;
}
```
2018-03-02 18:48:03 +00:00
The following files will be generated:
* `book.g.dart`
* `book.serializer.g.dart`
2018-03-02 18:55:03 +00:00
# Serialization
You can use the generated files as follows:
```dart
myFunction() {
var warAndPeace = new Book(
author: 'Leo Tolstoy',
title: 'War and Peace',
description: 'You will cry after reading this.',
pageCount: 1225
);
// Easily serialize models into Maps
var map = BookSerializer.toMap(warAndPeace);
// Also deserialize from Maps
var book = BookSerialize.fromMap(map);
print(book.title); // 'War and Peace'
// For compatibility with `JSON.encode`, a `toJson` method
// is included that forwards to `BookSerializer.toMap`:
expect(book.toJson(), map);
2018-03-09 12:39:21 +00:00
}
```
As of `2.0.2`, the generated output also includes information
about the serialized names of keys on your model class.
```dart
myOtherFunction() {
// Relying on the serialized key of a field? No worries.
map[BookFields.author] = 'Zora Neale Hurston';
}
2018-03-02 18:55:03 +00:00
}
```
## Customizing Serialization
Currently, these serialization methods are supported:
* to `Map`
* to JSON
You can customize these by means of `serializers`:
```dart
@Serializable(serializers: const [Serializers.map, Serializers.json])
class _MyClass extends Model {}
```
2017-06-17 01:56:38 +00:00
## Aliases
Whereas Dart fields conventionally are camelCased, most database columns
tend to be snake_cased. This is not a problem, because we can define an alias
for a field.
2017-06-20 22:13:04 +00:00
By default `angel_serialize` will transform keys into snake case. Use `Alias` to
provide a custom name, or pass `autoSnakeCaseNames`: `false` to the builder;
2017-06-17 01:56:38 +00:00
```dart
2017-06-17 02:00:24 +00:00
@serializable
2017-06-17 01:56:38 +00:00
abstract class _Spy extends Model {
/// Will show up as 'agency_id' in serialized JSON.
///
/// When deserializing JSON, instead of searching for an 'agencyId' key,
/// it will use 'agency_id'.
///
/// Hooray!
String agencyId;
2017-06-20 22:13:04 +00:00
@Alias('foo')
String someOtherField;
2017-06-17 01:56:38 +00:00
}
```
2018-03-02 18:48:03 +00:00
You can also override `autoSnakeCaseNames` per model:
```dart
@Serializable(autoSnakeCaseNames: false)
abstract class _OtherCasing extends Model {
String camelCasedField;
}
```
2017-06-17 01:56:38 +00:00
## Excluding Keys
In pratice, there may keys that you want to exclude from JSON.
To accomplish this, simply annotate them with `@exclude`:
```dart
2017-06-17 02:00:24 +00:00
@serializable
2017-06-17 01:56:38 +00:00
abstract class _Whisper extends Model {
/// Will never be serialized to JSON
@exclude
String secret;
}
```
2018-03-02 18:48:03 +00:00
There are times, however, when you want to only exclude either serialization
or deserialization, but not both. For example, you might want to deserialize
passwords from a database without sending them to users as JSON.
In this case, use `canSerialize` or `canDeserialize`:
```dart
@serializable
abstract class _Whisper extends Model {
/// Will never be serialized to JSON
///
/// ... But it can be deserialized
@Exclude(canDeserialize: true)
String secret;
}
```
2017-06-17 01:56:38 +00:00
# Nesting
`angel_serialize` also supports a few types of nesting of `@serializable` classes:
2018-03-02 18:48:03 +00:00
* As a class member, ex. `Book myField`
* As the type argument to a `List`, ex. `List<Book>`
* As the second type argument to a `Map`, ex. `Map<String, Book>`
2017-06-17 01:56:38 +00:00
In other words, the following are all legal, and will be serialized/deserialized.
2018-02-28 02:12:49 +00:00
You can use either the underscored name of a child class (ex. `_Book`), or the
generated class name (ex `Book`):
2017-06-17 01:56:38 +00:00
```dart
@serializable
abstract class _Author extends Model {
2018-03-02 18:48:03 +00:00
List<Book> books;
Book newestBook;
Map<String, Book> booksByIsbn;
2017-06-17 01:56:38 +00:00
}
2017-06-20 22:13:04 +00:00
```
2018-03-02 18:48:03 +00:00
If your model (`Author`) depends on a model defined in another file (`Book`),
then you will need to generate `book.g.dart` before, `author.g.dart`,
**in a separate build action**. This way, the analyzer can resolve the `Book` type.
2017-06-20 22:13:04 +00:00
# ID and Dates
This package will automatically generate `id`, `createdAt`, and `updatedAt` fields for you,
2018-03-02 18:48:03 +00:00
in the style of an Angel `Model`. To disable this, set `autoIdAndDateFields` to `false` in the
builder constructor.
You can also override `autoSnakeCaseNames` per model:
```dart
@Serializable(autoIdAndDateFields: false)
abstract class _Skinny extends Model {}
```