Rico Yao

The latest version needs to reflect: - No more use of AutoValue - Ability to check which fields are "set" - Updated usage pattern for TypeAdapters - Other minor changes

Make it easier to detect use of outdated Plank binary

3

In a codebase where developers manually execute the Plank binary to generate models, it is difficult to detect scenarios where they may be landing code based on an outdated Plank...

Consider adding an isValid method

4

It would be nice if there was a method had to check if the model is "valid" in the sense that it contains the non-optional set of fields as defined...

https://github.com/pinterest/plank/pull/187#discussion_r267147532 Currently we have to do: `Languages.java.snakeCaseToPropertyName(str)` We should have some kind of context that tells us what language we are in.

Previously it was renamed from "id" to "identifier" just because it was going through objC reserved keyword checks, but "uid" isn't any better. This was done for internal reasons, but...