v0.3.1

What's New?

• Added documentation
• Fixed a retain cycle

About <v1.0

I'm using this in production. YMMV.

Before a 1.0.0 release, this project follows a modified SemVer:

Reasonable effort is put forth to use Patch version Z (x.y.Z | x > 0) when new, backwards compatible functionality is introduced to the public API. And for Minor version Y (x.Y.z | x > 0) when any backwards incompatible changes are introduced to the public API.

v0.3.0

What's New?

• Updated for Swift 2.0
• Forms can push new view controllers, which can themselves contain forms
• Component registration system
• More public points of control

Between more public APIs and the component registration system, it's much easier to build custom row types. All text entry cells are now written using only public APIs.

About <v1.0

I'm using this in production, and the way I'm using works fine. YMMV.

Before a 1.0.0 release, this project follows a modified SemVer:

Reasonable effort is put forth to use Patch version Z (x.y.Z | x > 0) when new, backwards compatible functionality is introduced to the public API. And for Minor version Y (x.Y.z | x > 0) when any backwards incompatible changes are introduced to the public API.

So Many Dragons

I'm using this in production, and the way I'm using works fine. YMMV.

Before a 1.0.0 release, this project follows a modified SemVer. Instead of

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

Reasonable effort is put forth to use Patch version Z (x.y.Z | x > 0) when new, backwards compatible functionality is introduced to the public API. And for Minor version Y (x.Y.z | x > 0) when any backwards incompatible changes are introduced to the public API.