Missing signatures of functional interfaces
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- documentation
Research direction
Open the MarkdownPostProcessor documentation page named in the issue and compare its functional-interface documentation with the requested TypeScript signature. Add the missing signature, then verify that the page displays the HTMLElement, MarkdownPostProcessorContext, Promise, and void types as specified.
Written by the indexing model from the issue text.
Description
The docs page for https://docs.obsidian.md/Reference/TypeScript+API/MarkdownPostProcessor
is missing the following (the most essential) part
(el: HTMLElement, ctx: MarkdownPostProcessorContext): Promise<any> | void;
- Dominant language
- JavaScript
- Stars
- 532
- Forks
- 173
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from obsidianmd/obsidian-developer-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
obsidianmd/obsidian-developer-docs#265 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
obsidianmd/obsidian-developer-docs#262 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
obsidianmd/obsidian-developer-docs#252 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
obsidianmd/obsidian-developer-docs#242 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in obsidianmd/obsidian-developer-docs
Similar issues
-
enhancement p2 setup
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Query Log shows "Upstream" for CNAME cloaking, schedule, NXDOMAIN hijack and response IP blocksOpenbug good first issue query-log web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ferrous-networking/ferrous-dns#326 ·
Maintainers usually reply within 1 day
-
type: typos
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 4 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Ylianst/MeshCentral#8294 ·
Maintainers usually reply within 1 day