This document contains instructions for setting up Pest support for all of the supported editors.
The method of updating your config is editor specific.
The available options for all editors are:
{
// Check for updates to the Pest LS binary via crates.io
"pestIdeTools.checkForUpdates": true,
// Ignore specific rule names for the unused rules diagnostics (useful for specifying root rules)
"pestIdeTools.alwaysUsedRuleNames": [
"rule_one",
"rule_two"
]
}
- Download the extension.
- Await the prompt which will ask you if you want to install a suitable binary, and accept.
- Wait for it to install the server.
- If the server fails to install, you can install it manually using
cargo install pest-language-server
, then use the configurationpestIdeTools.serverPath
to point the extension to the installed binary.
- If the server fails to install, you can install it manually using
- (Optional) You may need to execute the command
Pest: Restart server
or reload your window for the server to activate.
These config options are specific to VSCode.
{
// Set a custom path to a Pest LS binary
"pestIdeTools.serverPath": "/path/to/binary",
// Custom arguments to pass to the Pest LS binary
"pestIdeTools.customArgs": []
}
- Download the
pest.sublime-package
file from the latest release's assets page.- This gives you syntax highlighting for Pest flies.
- Place the downloaded
pest.sublime-package
file in thepath/to/sublime-text/Installed Packages
directory. - Install the server using
cargo install pest-language-server
. - Execute the
Preferences: LSP Settings
command and add a new key to theclients
object.// LSP.sublime-settings "clients": { "pest": { "enabled": true, // This is usually something like /home/username/.cargo/bin/pest-language-server "command": ["/path/to/language/server/binary"], "selector": "source.pest", }, // ...other LSPs }
- You may have to restart your Sublime Text to get the LSP to start.