nextcloud / nextcloud/text

Allow to provide a custom placeholder

Open
#5,551 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 set the default value for the placeholder

Describe the solution you'd like
The Placeholder extension should use a placeholder option in RichText.js, which can be passed as a prop to Editor/MarkdownContentEditor and finally exposed to createEditor().

Describe alternatives you've considered
Adding my own configured instance of the Placeholder extension, if #5550 is available.

Or possibly directly changing the extension's configured value for the placeholder, if possible after the editor has loaded?

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 in RichText.js and trace how the placeholder option would pass through Editor/MarkdownContentEditor to OCA.Text.createEditor(). Confirm the Placeholder extension uses that value and that callers can provide it through the exposed editor API.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.