Note This project is in Alpha phase right now. Major changes might occur.
Just install the plugin to your preferred system, and it should plug into your project.
The current featureset is as follows:
- Provides Completions for custom elements defined in the local Custom Elements Manifest and ones in node_modules
- Provides type hints for attributes and properties on html tages
- Provides Go To Definition -functionality for Custom Elements defined in the Custom Elements Manifest
- Provides diagnostics on missing imports and unclosed custom element tags
For VS Code, you are able to install the Custom Elements Language Server through the extension Marketplace.
NeoVim supports LSP actions through the built in LSP. You will just need to install the Language Server locally on your machine through npm or yarn, and then enable your connector for the language service.
Install the server plugin from Npm
npm install -g custom-elements-languageserverCustom Elements Language Server is comes pre-configured with Mason and Nvim-lspconfig.
Configuration might change but at the moment it should look something like the following:
require'lspconfig'.custom_elements_ls.setup{}Is your favorite editor missing? If the editor supports LSP actions, plugging it in should be easy. If you need assistance, submit an issue.
The aim of the Custom Elements Language Server / Language services is to create a centralized server for supporting LSP operations on Custom Elements.
These operations include but are not limited to
- Go To Definition
- Attribute autocompletion
- Slot name autocompletions
- Event binding completions
Via installing a plugin to your favorite editor to support LSP actions, you are able to enable all of these Language Service functionalities.
You should only have a package.json, and a tsconfig.json (or a jsconfig.json) file in your project. So pretty much any Javascript/Typescript project will do!
The Custom Elements Language Server should provide you with completions and diagnostics anywhere where you are using html and custom elements.
The Custom Elements Language Server utilizes the Open WC CEM Analyzer and a bunch of custom tools to go through your codebase and provide useful analytics on your code.
You sure can! By providing a custom-elements-manifest.config.mjs in your project root, you can extend the capability of the analyzer itself, and the Custom Elements Language Server will also utilize these changes while doing it's own scanning through your project.
Sometimes CELS might catch some diagnostics that might not be useful for your usecase.
Adding a comment anywhere in your code with the given code, will disable diagnostics for said file.
These diagnostics can be disbled with the following flags:
| Command | Action |
|---|---|
| cels-disable-diagnostics | Disable all diagnostics |
| cels-disable-missing-closed | Disable diagnostics for non-closed custom element tags |
| cels-disable-import-check | Disable checks for non-imported custom elements |
