ractive v1.4.0 Release Notes

    • 🐛 Bug fixes

      • Embedded typings are improved: added missing methods and properties and improved extend support.
      • yields in non-isolated components will avoid creating implicit mappings by properly skipping the component fragment to the container fragment when resolving references (#3351).
      • Components initialized from a template will now call the component constructor. There's a new component: boolean property on init options passed to the constructor that is set to true when the view is initilizing the component. This also avoids double init.
      • An event handler removed while firing will no longer throw.
      • Context find methods now support the options that the instance versions support.
      • Custom elements are now checked in a hopefully more cross-browser way.
      • Links will now propagate changes that happen in their source models up to their parent model.
    • Experimental new features

      • Computation setter functions now receive a context argument, and both getter and setter functions now receive a keypath argument.
      • Component styles can be split into multiple managed style tags in the document head by setting Ractive.perComponentStyleElements to true.
      • Methods that set a single value will now return the new value as the resolution of the returned promise e.g. r.toggle('foo') if foo is falsey will return a promise that resolves to true. add/subtract/set behave similarly.
      • Decorators and custom events can now access their local context, in the case of a yielded attribute partial, with this.getLocalContext().