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

Globals should be derived from parsing lib files... #622

Open
kitsonk opened this issue Feb 23, 2021 · 0 comments
Open

Globals should be derived from parsing lib files... #622

kitsonk opened this issue Feb 23, 2021 · 0 comments
Labels
feature a new feature globals Issues related to acquiring symbols available globally

Comments

@kitsonk
Copy link
Contributor

kitsonk commented Feb 23, 2021

Instead of maintaining a hand crafted list of global variables, deno_lint should take either a list generated externally when the API is called, or parse a set of provided API files when the API is called.

With the generated list, the Deno CLI (or other consumer) would generate a list of global symbol names and pass in based on the ambient configuration.

The other option would be that Deno CLI (or other consumer) would supply a list of lib.*.d.ts files that are being applied to the program/files to be linted, which should be parsed so that their global symbols are extracted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a new feature globals Issues related to acquiring symbols available globally
Projects
None yet
Development

No branches or pull requests

2 participants