denoland / denoland/deno_graph
Remove "specifier" on `Range` when able or don't use `Range`
Open
breaking change
enhancement
- Dominant language
- Rust
- Stars
- 137
- Forks
- 47
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 4
Description
`specifier` on `Range` is largely duplicate information that can already be found based on what module someone is in. We should try to not store it when able.
> Also, we should probably remove the specifier property on Range because that's duplicate information that can be figured out by looking at the current module's specifier.
https://github.com/denoland/deno_graph/issues/247#issuecomment-1455350672
* Also, as part of this, Resolver's referrer_range's position should be made optional.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.