Typescript bug on value prop.

Open
#60 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript, webpack
Domain
frontend

Research direction

Reproduce the reported case in a Webpack 5 TypeScript project by rendering without a value prop, then compare its type-checking behavior with the documentation's required-prop declaration. Confirm that TypeScript reports the missing value prop while preserving the expected behavior for other required props.

Written by the indexing model from the issue text.

Description

I set my project with Webpack-5 and typescript. I got this error first time I rendered the <MDEditor /> without "value" prop.
md

I checked the documentation and looks like "value" prop is the only required prop but I did not get typescript warning. Typescript gives me warning for other packages's required props so ts configuration in my project is correct. I though this might be a bug.

Dominant language
TypeScript
Stars
382
Forks
37
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from uiwjs/react-markdown-editor

All issues in uiwjs/react-markdown-editor

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.