@Renzo-Olivares looks like you've got multiple test failures in this PR. At first glance, they look to be related to the API you're updating.

@matthew-carroll It looks like it might be because the super_editor package needs to be updated, and that update rolled into packages that depend on it like super_editor_clipboard, super_editor_markdown, and super_editor_quill. If so, is that something I should do in this PR?

@Renzo-Olivares for this PR at this stage, if you need other packages in the mono-repo to use your super_editor changes, then you should change the pubspec for each of those packages by adding a dependency override that points to the local version of super_editor. E.g.:

dependency_overrides:
  super_editor:
    path: ../super_editor

@matthew-carroll I updated the dependencies to use the local copy of super_editor but I think i've hit a snag. super_editor_quill and super_editor_markdown were recently moved into super_editor and those packages are only compatible with older versions of super_editor. Adding a local override ends up causing import conflicts because classes are defined in both super_editor and the sub-package. If the plan is to move those packages into super_editor should I go ahead and delete the sub-package implementations to fix the conflicts?

@Renzo-Olivares that's a good question. Let me think about it. We might just merge as-is and deal with it later. We'll see. I plan to get this PR merged in the next day or two.

@Renzo-Olivares I deleted those pckages. I'm going to attempt to pull down your branch and rebase it. We'll see how it goes.

@Renzo-Olivares gonna close this PR in favor of the copy I put up with adjustments for the removal of those 2 packages: #2950