How is difficulty level evaluated? #109
-
|
@Priyanshu-byte-coder I was curious about how the difficulty level is decided by the maintainers. :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Good question! Here is roughly how I evaluate it: Beginner (20 pts) — Self-contained changes to a single component or file, no new APIs, minimal state logic. Things like fixing a UI bug, adding a loading state, or a small visual improvement. Intermediate (35 pts) — Spans 2–4 files, involves some API work or non-trivial state management. A new widget with its own endpoint, or a feature that touches both frontend and backend. Advanced (55 pts) — Cross-cutting features that require schema changes, multiple new endpoints, auth considerations, or significant architectural decisions. Something like the public profile feature — DB migration, two new API routes, a new page with SEO metadata. Critical (80 pts) — Reserved for security fixes, major refactors that touch most of the codebase, or anything that requires deep understanding of the full stack. The quality multipliers (×1.2 for If you ever feel a label does not match the actual complexity of your PR, feel free to comment and I will take another look! |
Beta Was this translation helpful? Give feedback.
Good question! Here is roughly how I evaluate it:
Beginner (20 pts) — Self-contained changes to a single component or file, no new APIs, minimal state logic. Things like fixing a UI bug, adding a loading state, or a small visual improvement.
Intermediate (35 pts) — Spans 2–4 files, involves some API work or non-trivial state management. A new widget with its own endpoint, or a feature that touches both frontend and backend.
Advanced (55 pts) — Cross-cutting features that require schema changes, multiple new endpoints, auth considerations, or significant architectural decisions. Something like the public profile feature — DB migration, two new API routes, a new page with SEO metadata.
Crit…