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.

Sign up for GitHub

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

Jump to bottom

Add JSON schemas for Emmet config files #19255

Closed
chrmarti opened this issue Jan 24, 2017 · 1 comment
Closed

Add JSON schemas for Emmet config files #19255

chrmarti opened this issue Jan 24, 2017 · 1 comment
Assignees
@ramya-rao-a
Labels
emmet Emmet related issues

Comments

@chrmarti
Copy link
Contributor

chrmarti commented Jan 24, 2017 •
edited
Loading

Test item #19079

  • VSCode Version: Code - Insiders 1.9.0-insider (4265f5e, 2017-01-24T10:29:13.076Z)
  • OS Version: Darwin x64 15.6.0
  • Extensions: None

Not sure if there is an easy way to do that since the file names are not Emmet-specific, but given the "emmet.extensionsPath" we know what they are. /cc @aeschli
@chrmarti chrmarti added the emmet Emmet related issues label Jan 24, 2017
@ramya-rao-a
Copy link
Contributor

I personally vote this down

The new apis from Emmet 2.0 follow a different format and @sergeche has plans to make it easier for people to write these files.

Given this and the fact that there are current instructions in the emmet website
(https://docs.emmet.io/customization/) , I'd say there is not much ROI in us maintaining schemas for emmet customization files

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ramya-rao-a ramya-rao-a

Labels
emmet Emmet related issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrmarti @ramya-rao-a