Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove "specifier" on Range when able or don't use Range #263

Open
dsherret opened this issue Apr 3, 2023 · 0 comments
Open

Remove "specifier" on Range when able or don't use Range #263

dsherret opened this issue Apr 3, 2023 · 0 comments
Labels
breaking change enhancement New feature or request

Comments

@dsherret
Copy link
Member

dsherret commented Apr 3, 2023

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.

#247 (comment)

  • Also, as part of this, Resolver's referrer_range's position should be made optional.
@dsherret dsherret added enhancement New feature or request breaking change labels Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant