niieani/typescript-vs-flowtype

Add objective error quality comparison

Open

#36 opened on Jun 7, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees) (76 forks)github user discovery
help wanted

Repository metrics

Stars
 (1,727 stars)
PR merge metrics
 (PR metrics pending)

Description

Flow 66 improved a lot error messages

https://medium.com/flow-type/better-flow-error-messages-for-the-javascript-ecosystem-73b6da948ae2

I think it got better than Typescript

Contributor guide

Research direction
Gather examples of similar errors from both Flow and TypeScript, and compare the quality of error messages based on clarity, helpfulness, and context.
Tech stack
typescriptjavascript
Domain
developer experience
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70