Ensuring change events are also triggered on `radiochange`

#206

Fixing support for Steal 0.16

#204

v3.1.0

• Handle spaces in event binding syntax (ex: (. some-prop))
• Registered stache helpers now work as attribute values for events (ex: (some-event)="registeredHelper")
• Update attribute compute to use radiochange for radio checked
• Add "parent value undefined" test
• Add test for one-way binding checkboxes to undefined

v3.0.19

Fixing tests

Make the tests pass consistently

Stache bindings have a lot of moving parts underneath: computes, lifecycle events, mutation observers, etc, plus they must run in real DOM and vdom. Getting the timings right for evaluating state in the test battery has been difficult, so in these recent releases we've researched what was causing the test failures and taken steps to prevent them from breaking in CI.

[Deprecated] use v3.0.18 or later

This release includes a non-polyfilled call to setImmediate (via can-compute v3.0.9) which is not supported on all platforms. Use v3.0.18 which requires the non-deprecated can-compute v3.0.10

[Deprecated] interim testing release

use v3.0.18 or later if you include the can-stache-bindings tests in your test suite.

There are no code changes since the previous release.

v3.0.15

Fixes #169, #123, #127, and #170.

Make two-way bindings sticky

• Two-way bindings are now properly "sticky" -- a conversion on one end that doesn't change the value from previous (e.g. inputting the same thing with different case, when the other end of the binding lowercases the value) will still ensure that the other end still triggers a setter.
• The docs were also updated to fix some outdated terminology.

Remove deprecated "attr" method

#154