@bigbinary/neeto-editor 1.31.3-beta.0 → 1.31.3-beta.1

package/README.md

@@ -8,6 +8,12 @@ The **neetoEditor** library drives the rich text experience in the
 yarn add @bigbinary/neeto-editor
 ```
 
+## Dependencies
+
+**neetoEditor** has few peer dependencies which are required to use neetoEditor
+properly. Make sure you install all the peerDependencies mentioned in the
+[package.json](./package.json)
+
 For setting up image upload refer
 https://neeto-editor.neeto.com/?path=/docs/examples-customize-options-addons--addons.
 
@@ -22,62 +28,82 @@ yarn
 Running the `yarn storybook` command starts a storybook application. Use this
 application to test out changes.
 
-When developing frontend packages, it's crucial to test changes in a live environment using a host application.
-There are two ways to do this:
+When developing frontend packages, it's crucial to test changes in a live
+environment using a host application. There are two ways to do this:
 
 1. Using yalc package manager: https://youtu.be/F4zZFnrNTq8
 
-> Note: If you are using yalc, you need to run `yarn bundle` after making changes to the package instead of `yarn build` which is described in the video.
+> Note: If you are using yalc, you need to run `yarn bundle` after making
+> changes to the package instead of `yarn build` which is described in the
+> video.
 
 2. Directly updating the node_modules of the host application.
 
-    1. Start the host application server
-    2. Inside the package, execute the command:
+   1. Start the host application server
+   2. Inside the package, execute the command:
 
-        ```
-          yarn bundle --watch --app ../neeto-site-web
-        ```
+      ```
+        yarn bundle --watch --app ../neeto-site-web
+      ```
 
-        Here replace ../neeto-site-web with path to the host project.
+      Here replace ../neeto-site-web with path to the host project.
 
-        Now, any changes made to the neetoEditor codebase will be instantly reflected in the UI.
+      Now, any changes made to the neetoEditor codebase will be instantly
+      reflected in the UI.
 
-    3. Remove local installation
+   3. Remove local installation
 
-        Run the following command to reset to the initial state.
-        ```
-        yarn install --check-files
-        ```
+      Run the following command to reset to the initial state.
 
-    4. Translation File Changes (optional)
+      ```
+      yarn install --check-files
+      ```
 
-        Modifications in the neeto-editor translation files will not automatically update the UI. To verify these changes, update your neeto-site-web/app/javascript/packs/application.js file with the following code:
+   4. Translation File Changes (optional)
 
-        ```
-        import en from "translations/en.json";
+      Modifications in the neeto-editor translation files will not automatically
+      update the UI. To verify these changes, update your
+      neeto-site-web/app/javascript/packs/application.js file with the following
+      code:
 
-        import editorEn from "neetofilters/app/javascript/src/translations/en.json";
+      ```
+      import en from "translations/en.json";
 
-        import { mergeDeepLeft } from "ramda";
+      import editorEn from "neetofilters/app/javascript/src/translations/en.json";
 
-        initializeApplication({
-          translationResources: { en: { translation: mergeDeepLeft(editorEn, en) } },
-        });
-        ```
+      import { mergeDeepLeft } from "ramda";
+
+      initializeApplication({
+        translationResources: { en: { translation: mergeDeepLeft(editorEn, en) } },
+      });
+      ```
 
 ## Instructions for Publishing
 
 ### Package Release Process
 
-A package is released upon merging a PR labeled as patch, minor, or major into the main branch. The patch label addresses bug fixes, minor signifies the addition of new features, and major denotes breaking changes, adhering to the principles outlined in [Semantic Versioning (SemVer)](https://semver.org/).
+A package is released upon merging a PR labeled as patch, minor, or major into
+the main branch. The patch label addresses bug fixes, minor signifies the
+addition of new features, and major denotes breaking changes, adhering to the
+principles outlined in [Semantic Versioning (SemVer)](https://semver.org/).
 
-You can checkout the Create and publish releases workflow in GitHub Actions to get a live update.
+You can checkout the Create and publish releases workflow in GitHub Actions to
+get a live update.
 
 ### Manual Package Publishing
 
-If you missed adding the label, you can manually publish the package. For that first, you need to create a PR to update the version number in the package.json file and merge it into the main branch. After merging the PR, you need to create a [new GitHub release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository) from the main branch. Whenever a new release is created with a new version number, the GitHub actions will automatically publish the built package to npm. You can check out the Publish to npm workflow in GitHub Actions to get a live update.
-
-> Note: before publishing the package, you must verify the functionality in host application [locally](#instructions-for-development).
+If you missed adding the label, you can manually publish the package. For that
+first, you need to create a PR to update the version number in the package.json
+file and merge it into the main branch. After merging the PR, you need to create
+a
+[new GitHub release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository)
+from the main branch. Whenever a new release is created with a new version
+number, the GitHub actions will automatically publish the built package to npm.
+You can check out the Publish to npm workflow in GitHub Actions to get a live
+update.
+
+> Note: before publishing the package, you must verify the functionality in host
+> application [locally](#instructions-for-development).
 
 ## Documentation
 

package/index.cjs.js

@@ -40507,8 +40507,9 @@ var EmojiPickerMenu = /*#__PURE__*/function (_React$Component) {
       return false;
     });
     _defineProperty(_this, "handleSelect", function (emoji) {
+      var _this$props$setActive, _this$props;
       _this.props.editor.chain().focus().deleteRange(_this.props.range).setEmoji(emoji).run();
-      _this.props.setActive(false);
+      (_this$props$setActive = (_this$props = _this.props).setActive) === null || _this$props$setActive === void 0 || _this$props$setActive.call(_this$props, false);
     });
     return _this;
   }
@@ -40549,9 +40550,9 @@ EmojiPickerMenu.defaultProps = {
 
 function ownKeys$e(e, r) { var t = Object.keys(e); if (Object.getOwnPropertySymbols) { var o = Object.getOwnPropertySymbols(e); r && (o = o.filter(function (r) { return Object.getOwnPropertyDescriptor(e, r).enumerable; })), t.push.apply(t, o); } return t; }
 function _objectSpread$e(e) { for (var r = 1; r < arguments.length; r++) { var t = null != arguments[r] ? arguments[r] : {}; r % 2 ? ownKeys$e(Object(t), !0).forEach(function (r) { _defineProperty(e, r, t[r]); }) : Object.getOwnPropertyDescriptors ? Object.defineProperties(e, Object.getOwnPropertyDescriptors(t)) : ownKeys$e(Object(t)).forEach(function (r) { Object.defineProperty(e, r, Object.getOwnPropertyDescriptor(t, r)); }); } return e; }
+var EmojiPickerPluginKey = new PluginKey("emoji-picker");
 var EmojiPicker = Node.create({
-  name: "emoji-picker",
-  key: new PluginKey("emoji-picker"),
+  name: "emojiPicker",
   group: "inline",
   inline: true,
   selectable: false,
@@ -40561,7 +40562,7 @@ var EmojiPicker = Node.create({
       suggestion: {
         "char": "::",
         startOfLine: false,
-        pluginKey: new PluginKey("emoji-picker-suggestions"),
+        pluginKey: EmojiPickerPluginKey,
         items: function items() {
           return [];
         },
@@ -41334,8 +41335,6 @@ var linkInputRule = function linkInputRule(config) {
   });
 };
 var Link = extensionLink.Link.extend({
-  name: "custom-link",
-  key: new PluginKey("custom-link"),
   inclusive: false,
   addAttributes: function addAttributes() {
     var _this$parent;
@@ -41562,8 +41561,6 @@ var suggestion$1 = {
   }
 };
 var Mentions$1 = Mention__default["default"].extend({
-  name: "mentions",
-  key: new PluginKey("mentions"),
   addCommands: function addCommands() {
     var _this = this;
     return {
@@ -42559,6 +42556,7 @@ var SlashCommands = {
 var _excluded$6 = ["suggestion"];
 function ownKeys$7(e, r) { var t = Object.keys(e); if (Object.getOwnPropertySymbols) { var o = Object.getOwnPropertySymbols(e); r && (o = o.filter(function (r) { return Object.getOwnPropertyDescriptor(e, r).enumerable; })), t.push.apply(t, o); } return t; }
 function _objectSpread$7(e) { for (var r = 1; r < arguments.length; r++) { var t = null != arguments[r] ? arguments[r] : {}; r % 2 ? ownKeys$7(Object(t), !0).forEach(function (r) { _defineProperty(e, r, t[r]); }) : Object.getOwnPropertyDescriptors ? Object.defineProperties(e, Object.getOwnPropertyDescriptors(t)) : ownKeys$7(Object(t)).forEach(function (r) { Object.defineProperty(e, r, Object.getOwnPropertyDescriptor(t, r)); }); } return e; }
+var SpecialMentionPluginKey = new PluginKey("special-mention");
 var renderLabel = function renderLabel(_ref) {
   var _node$attrs$label;
   var options = _ref.options,
@@ -42567,7 +42565,7 @@ var renderLabel = function renderLabel(_ref) {
 };
 var suggestion = {
   "char": "@@",
-  pluginKey: new PluginKey("special-mention-suggestions"),
+  pluginKey: SpecialMentionPluginKey,
   render: function render() {
     var reactRenderer;
     var popup;
@@ -42612,8 +42610,7 @@ var suggestion = {
   }
 };
 var SpecialMentions = Mention__default["default"].extend({
-  name: "special-mentions",
-  key: new PluginKey("special-mentions"),
+  name: "special-mention",
   renderHTML: function renderHTML(_ref2) {
     var node = _ref2.node,
       HTMLAttributes = _ref2.HTMLAttributes;