denoland / denoland/deno_graph
Validation should follow descendents
- Dominant language
- Rust
- Stars
- 137
- Forks
- 47
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 4
Description
When validating a graph and reaching a type branch, current behaviour descends into the children imports, treating them as code imports, and therefore erroring when there is a type branch only error, which it shouldn't.
See: https://github.com/denoland/deno/issues/15295
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Deno issue 15295 and tracing validation when the graph reaches a type branch. The payload names no source files, tests, or entry points, so first identify the validation path and its existing reproduction; done means type-only descendants no longer produce code-import validation errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100