v0.17.0

Stipple v0.17.0

Diff since v0.16.0

Closed issues:

• how can I get something like '
  ' ? (#54)

Merged pull requests:

• Add missing StippleUI to Example 2 (#69) (@roflmaostc)

v0.16.0

Stipple v0.16.0

Diff since v0.15.0

Closed issues:

• [improvement] Please provide wrap of plotly ! (#21)
• Make the server side code work without connected clients (initialize channels) (#50)

v0.15.0

Stipple v0.15.0

Diff since v0.14.0

Merged pull requests:

• Added support for v-for directive (#64) (@AbhimanyuAryan)

v0.14.0

Stipple v0.14.0

Diff since v0.13.0

v0.13.0

Stipple v0.13.0

Diff since v0.12.0

v0.12.0

Stipple v0.12.0

Diff since v0.11.6

v0.11.6

Fix typos for payload and wsclient

v0.11.5

• compatibility with Genie 2
• support Union types
• fix issue in java script

set version v0.11.4

compatibility with Observables < v0.4

set version v0.11.3

fix an issue with Observables.map! for Reactive types:

julia> r = Reactive(true)
Reactive{Bool}(Observable{Bool} with 0 listeners. Value:
true, 0, false, false)

julia> o = Observable(false)
Observable{Bool} with 0 listeners. Value:
false

julia> map!(any, r, o)
Observable{Bool} with 0 listeners. Value:
false

support data that reside on the client side only:

  `function client_data(app::T)::String where {T<:ReactiveModel}`

  Defines additional data that will only be visible by the browser.

  It is meant to keep volatile data, e.g. form data that needs to pass a validation first. In order to use the data you most probably also want to define js_methods

  Example
  –––––––––

  import Stipple.client_data
  client_data(m::Example) = client_data(client_name = js"null", client_age = js"null", accept = false)

  will define the additional fields client_name, clientage and accept for the model Example. These should, of course, not overlap with existing fields of your model.