StateView changelog

Changelog History

• v2.0 Changes

  September 14, 2016

  2.0

  🚀 Released on September 15th, 2016

  ➕ Additions

  • 👍 Swift 3 support

• v1.3 Changes

  May 19, 2016

  1.3

  🚀 Released on May 19th, 2016

  ➕ Additions

  • ⚡️ You can now use viewDidInitialize(), viewWillUpdate(newState, newProps), and viewDidUpdate() to run code at special points in the lifetime of your view.
    • viewDidInitialize() is called when your StateView subclass is initialized and has received its initial state and props.
    • viewWillUpdate(newState, newProps) is called after your StateView subclass receives new values in state or props and is about to update its subviews. This method is not called when your view is initialized.
    • viewDidUpdate() is called after your StateView has updated its subviews after receiving new values in state or props. This method is not called when your view is initialized.

• v1.2 Changes

  May 15, 2016

  1.2

  🚀 Released on May 15th, 2016

  ➕ Additions

  • The renderDeep() method of StateView is now public.

• v1.1 Changes

  April 27, 2016

  1.1

  🚀 Released on April 26th, 2016

  ➕ Additions

  • 📚 You can now keep instances of any type in props and state, and pass instances of any type between views. See the latest documentation for more information.

• v1.0 Changes

  April 25, 2016

  1.0

  🚀 Released on April 25th, 2016

  ➕ Additions

  • 📚 You can now pass values between views by naming them with an enum of your choice. With enums, the names you have chosen for your values are clearer to see together and can make use of Xcode's built-in autocomplete. To use an enum of your choice, create an enum that conforms to the StateKey protocol. See the latest documentation for more information.

  🗄 Deprecations

  • You can no longer name values being passed between views with Strings. Use an enum of your choice that conforms to the StateKey protocol.

• v0.2

  April 09, 2016

• v0.1

  April 07, 2016

• v0.0

  April 09, 2016