Skip to content

WIP: Ember addon v2 format with Froala Editor v5 update#174

Draft
Panman82 wants to merge 16 commits into
masterfrom
v5-dev
Draft

WIP: Ember addon v2 format with Froala Editor v5 update#174
Panman82 wants to merge 16 commits into
masterfrom
v5-dev

Conversation

@Panman82
Copy link
Copy Markdown
Contributor

Resetting the addon by deleting the previous files and re-ran ember addon using @ember/addon-blueprint with pnpm and typescript flags. Will be re-implementing components and editors using the latest ember.js "polaris edition" methodologies.

Deleted the previous files and re-ran `ember addon` using `@ember/addon-blueprint` with pnpm and typescript flags
Bring back the original start-year of 2016, update current year to 2026 (10 years!!)
Properties related to the repo and not package/addon configuration
`pnpm install froala-editor --save`
ember-cli does not natively support v2 addon format just yet, so this addon is to fill that gap to help generate files in the new format.
Modifiers are not yet built into ember.js and the `ember-modifier` package is meant to bridge the gap. This is need to access the `element` to init the Froala Editor.
It's alive, muhahaha!! Long ways to go though...
Ex: `<FroalaEditor @toolbarBottom={{true}} />`
For the latest addon v2 blueprint changes.
Allows destructuring rest properties without triggering "unused variable" errors for sibling properties. Ex: `const { unused, ...rest } = props`
Ability to pass options as one arg or individual args with the option names.
Strange issue with linting and testing, ran `pnpm install`
Nuf said
Apparently `editorInstance?: FroalaEditor` does not allow `null` when destroying the editor...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant