nextcloud / nextcloud/text

Allow to provide custom extensions

Open
#5,550 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Is your feature request related to a problem? Please describe.
When using the editor from another app with OCA.Text.createEditor, I can't provide my own extensions.

Describe the solution you'd like
A new option in the function argument object to provide a list of extensions to load. These should be passed to Editor/MarkdownContentEditor as props and injected into the tiptap editor itself.

Describe alternatives you've considered
Injecting the extension after the editor has loaded, if possible?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at OCA.Text.createEditor and trace how its function arguments reach Editor/MarkdownContentEditor. Check how props are passed into the tiptap editor, then verify that a supplied list of custom extensions is accepted and loaded when creating the editor.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.