Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@shsteimer
Copy link
Contributor

Description

wrap addColumnBefore and addColumnAfter to ensure when doing these from block header, header maintains correct col span

Related Issue

Motivation and Context

just trying to make things easier to use and prevent modifications that don't make sense in context

How Has This Been Tested?

locally at http://localhost:3000/edit#/aem-sandbox/block-collection/drafts/shsteimer/blocks-

new unit tests on table modifications to document/confirm behaviors

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Copy link
Member

@auniverseaway auniverseaway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small organizational fix, otherwise this is good.


import { InputRule, inputRules } from 'prosemirror-inputrules';

/**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would follow the existing pattern and not write code directly in this file. The basics seem fine, though.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refactored to use a plugin. Overall think it's a reasonably clean approach, but I won't be heart broken if you tell me this works as designed and isn't worth the trouble, as the default behavior does appear to match word

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.

3 participants