Break version lockstep between froala-editor and ember-froala-editor

[apellerano-pw]

This addon would have more freedom for the ember community to improve it if it wasn't required by froala org to keep version lockstep with froala-editor version.

There are two issues with ember-froala-editor that I'm aware of

1. froala-editor should be positioned as a peerDependency and not a dependency.
   • It's up to the consuming Ember Apps to specify a version of froala-editor that satisfies the peer semver range
2. It exists halfway between V1 and V2 Ember Addon.
   • It needs to update to V2 Addon to address Consider a way to exclude assets (plugins, third parties) from the build (v4+) #164
   • or regress to V1 style imports for froala's plugins by using broccoli instead of ember-auto-import

All of these are breaking changes as defined by semver. Semver is the officially recommended versioning system for npm packages with first-party support by all npm tooling. ember-froala-editor is distributed via npm.

What will it take to remove the version lockstep requirement so that this package can use semver to distribute bugfixes and enhancements, without waiting for unrelated updates to happen to froala-editor itself?

[Panman82]

It's been some time since I've talked to anyone at Froala, let me see if I can get in touch them again. I have some travel time coming up and could work on v2 format, maybe we roll with a "beta" channel until Froala Editor v5 is release... 😅

[apellerano-pw]

That's a good idea, could ship changes as e.g. 4.5.0-beta.1, 4.5.0-beta.2 etc. But I worry that will create a long-lived fork in the maintenance structure and double the effort to release patches. I don't know the timeline for a v5 Froala Editor; it could be very far away.

Could you get someone from the Froala org that owns this repo to weigh in to the conversation here? It would be helpful to understand why they want these packages to stay in lockstep. I can also reach out to their technical support as a paying customer if you think that will help.

[Panman82]

Actually I would run a beta branch in this repo and release v5 betas. If I remember right, it's actually similar when v4 came about, I had changed this addon to Octane Edition and ran a bunch of "betas" (although they were perfectly stable) before the official editor v4 release.

The reason Froala folks wanted lock-step was so all the integrations matched the editor version when new releases came out, so that it was clear what version the addon was providing too. With peer dependancies, now the addon doesn't have to be responsible for installing the editor so I'm hopeful we can break away from lock-step.

I've reached out to my Froala contacts but haven't heard back just yet.