Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.

Expose Linter as a global for devtools usage #414

Open
not-an-aardvark opened this issue Sep 26, 2017 · 1 comment
Open

Expose Linter as a global for devtools usage #414

not-an-aardvark opened this issue Sep 26, 2017 · 1 comment
Labels
documentation Relates to ESLint's documentation enhancement This change enhances an existing feature of the website

Comments

@not-an-aardvark
Copy link
Member

When reading API documentation, it's convenient to be able to try out the API in DevTools without leaving the documentation page. I think we should set window.Linter on eslint.org to the prebuilt Linter class.

Other sites that do this:
@eslintbot eslintbot added the triage An ESLint team member will look at this issue soon label Sep 26, 2017
@not-an-aardvark
Copy link
Member Author

I think before we do this, we should finish removing all the undocumented API surface from Linter (see eslint/eslint#9161). I don't want people to see properties in devtools and assume that the properties are intended to be used by API consumers.

@kaicataldo kaicataldo added documentation Relates to ESLint's documentation enhancement This change enhances an existing feature of the website and removed triage An ESLint team member will look at this issue soon labels Jun 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
documentation Relates to ESLint's documentation enhancement This change enhances an existing feature of the website
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kaicataldo @not-an-aardvark @eslintbot