Mapping

[DikieDick]

Roadmap:

• Code cell at the start of the document does not work (assigned to @XyntaxCS)
• Inserting does not yet work in prosemirror
  a. Inserting above fails to insert the proper newline after the inserted node?
  b. Inserting below also does not always insert the proper newline after the inserted node.
• Test mapping features from blocks instead of document constructor.
• Parse empty text nodes in .v file case (assigned to @DikieDick)
• Should we rename innerRange to contentRange? Also renamed range to tagRange as per suggestion by @XyntaxCS. (@DikieDick)
• Inserting does not yet work in mapping?
• Inserting below after input area inserts correctly but then mapping is off.
  a. It does work when the node selection is a markdown cell.
• We might not be able to fully remove the skull feature, as codemirror steps are applied and then send to prosemirror.
• Unit test coverage.
• Problem: Inserting below than moving into the inserted cell and inserting code cell again below crashes.
• Use more efficient searching algorithms. We have the invariant that the childnodes in the tree are sorted, hence we can use binary search, or use some more efficient tree searching algorithm (@DikieDick research). Tree method findNodeByProsePos uses binary search already.
• Check wpWrapIn and wpLift
• Why do we have pmRange and prosemirrorStart/prosemirrorEnd?

Resolves #33 and #28

[sonarqubecloud]

Quality Gate failed

Failed conditions
48.8% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate failed

Failed conditions
49.8% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud