Release 2.4.0 - BREAKING CHANGES

This release includes many changes to better align with embers philosophies. Because the version of this addon aligns with the froala-editor version, we could not release a new major version "out-of-line". Please make note of the following changes required when updating from <= 2.3 to >= 2.4.

Ember Compatibility Change

From 1.13+
To 2.3+

{{froala-editor}} Breaking Changes

• content is no longer updated by the editor, instead use an action to update the value. Ex:
  • From: {{froala-editor content=myProp}}
  • To: {{froala-editor content=myProp update=(action (mut myProp))}}
  • However, changes coming in to the component will update the editor. The component basically treats it like: {{froala-editor content=(readonly myProp)}}
• options changed post-initialization no longer updates the editor, instead use the related froala-editor methods
  • The component basically treats it like: {{froala-editor options=(unbound myOptions)}}
• Event handlers/actions on-*=(action) no longer receive an "event" object as the first arg, due to a change in event management. Change your action function signatures;
  • From: function( eventObject, editorComponenet, ...params ){}
  • To: function( editorComponenet, ...params ){}
  • Similarly for the on-*-getHtml actions, but the eventObject is the second argument
• contentBindingEvent attribute has been changed to updateEvent, in relation to the new update action
• defaultContent option has been removed, it was deemed unneeded and content is now set directly on the editor instance (previously rendered in the component template)
• Previously undocumented isSafeString attribute was renamed to returnSafeString

New Features

• Positional Params - Both components support positional params for certain attributes
  • {{froala-editor myProp (action (mut myProp)) (hash minHeight=100)}}
  • {{froala-editor content=myProp update=(action (mut myProp)) options=(hash minHeight=100)}}
  • {{froala-content myProp}}
  • {{froala-content content=myProp}}
• {{froala-editor}} update action and event name attributes
  • update is an action called when the updateEvent is triggered and passes the editors html content as the first argument
  • updateEvent is the froala editor event name which will call the update action

content mutation was removed because it better aligns with ember's direction for "data down, actions up" (similar to ember-one-way-controls). This and unmutable options also removed the need to maintain other complex state management.

Note: The {{froala-content}} component and other helpers did not undergo other major changes.

Release 2.4.0-rc.1

Changes between 2.3.6-beta.2 and 2.4.0-rc.1

• Bump ember deps to 2.10
• Bump froala-editor to 2.4.0-rc.1

Breaking changes between v2.3.5 and v2.4.0!!!

Because the version of this addon aligns with the froala-editor version, we could not release a new major version "out-of-line". Please note the following breaking changes to the {{froala-editor}} component;

• content is no longer updated by the editor, instead use an action to update the value. Ex:
  • From: {{froala-editor content=myProp}}
  • To: {{froala-editor content=myProp update=(action (mut myProp))}}
  • Alternate, "new" positional params option: {{froala-editor myProp (action (mut myProp))}}
• options changed post-initialization no longer updates the editor, instead use the related froala-editor methods
• Event handlers/actions on-*=(action) no longer receive an "event" object as the first arg, due to a change in event management. Change your action signatures;
  • From: function( eventObject, editorComponenet, ...params ){}
  • To: function( editorComponenet, ...params ){}
  • Similarly for the on-*-getHtml actions, but the eventObject is the second argument
• contentBindingEvent option has been removed, in related to the above content change
• defaultContent option has been removed, it was deemed unneeded and content is now set directly on the editor
• Previously undocumented isSafeString option was renamed to returnSafeString

content mutation was removed because it better aligns with ember's direction for "data down, actions up" (similar to ember-one-way-controls). This and unmutable options also removed the need to maintain other complex state management.

Release 2.3.6-beta.2

Changes between 2.3.6-beta.1 and 2.3.6-beta.2

• Added update and updateEvent options to the {{froala-editor}}
  • update is an action called when the updateEvent is triggered, taking a cue from ember-one-way-controls
  • updateEvent is the froala editor event name which will call the update action
• Added a few depreciation warnings to help with the 2.3.5 to 2.3.6 transition

Breaking changes between v2.3.5 and v2.3.6!!!

Because the version of this addon aligns with the froala-editor version, we could not release a new major version "out-of-line". Please note the following breaking changes to the {{froala-editor}} component;

• content is no longer updated by the editor, instead use an action to update the value. Ex:
  • From: {{froala-editor content=myProp}}
  • To: {{froala-editor content=myProp update=(action (mut myProp))}}
  • Alternate, "new" positional params option: {{froala-editor myProp (action (mut myProp))}}
• options changed post-initialization no longer updates the editor, instead use the related froala-editor methods
• Event handlers/actions on-*=(action) no longer receive an "event" object as the first arg, due to a change in event management. Change your action signatures;
  • From: function( eventObject, editorComponenet, ...params ){}
  • To: function( editorComponenet, ...params ){}
  • Similarly for the on-*-getHtml actions, but the eventObject is the second argument
• contentBindingEvent option has been removed, in related to the above content change
• defaultContent option has been removed, it was deemed unneeded and content is now set directly on the editor
• Previously undocumented isSafeString option was renamed to returnSafeString

content mutation was removed because it better aligns with ember's direction for "data down, actions up" (similar to ember-one-way-controls). This and unmutable options also removed the need to maintain other complex state management.

Release 2.3.6-beta.1

Breaking changes between v2.3.5 and v2.3.6!!!

Because the version of this addon aligns with the froala-editor version, we could not release a new major version "out-of-line". Please note the following breaking changes to the {{froala-editor}} component;

• content is no longer updated by the editor, instead use an action to update the value. Ex:
  • From: {{froala-editor content=myProp}}
  • To: {{froala-editor content=myProp on-contentChanged-getHtml=(action (mut myProp))}}
  • Alternate, "new" positional params option: {{froala-editor myProp (action (mut myProp))}}
• options changed post-initialization no longer updates the editor, instead use the related froala-editor methods
• Event handlers/actions on-*=(action) no longer receive an "event" object as the first arg, due to a change in event management. Change your action signatures;
  • From: function( eventObject, editorComponenet, ...params ){}
  • To: function( editorComponenet, ...params ){}
  • Similarly for the on-*-getHtml actions, but the eventObject is the second argument
• contentBindingEvent option has been removed, in related to the above content change
• defaultContent option has been removed, it was deemed unneeded and content is now set directly on the editor
• Previously undocumented isSafeString option was renamed to returnSafeString

content mutation was removed because it better aligns with ember's direction for "data down, actions up" (similar to ember-one-way-controls). This and unmutable options also removed the need to maintain other complex state management.

Release 2.3.5

Merge branch 'master' of github.com:froala/ember-froala-editor

Release 2.3.4

v2.3.4

2.3.4

Release 2.3.4

2.3.4

Release 2.3.3

Merge branch 'master' of https://github.com/froala/ember-froala-editor

Release 2.3.2

v2.3.2

2.3.2

Release 2.3.1

v2.3.1

2.3.1