https://github.com/catalalang/catala-language-server
Catala VSCode extension and LSP server
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (11.8%) to scientific vocabulary
Repository
Catala VSCode extension and LSP server
Basic Info
- Host: GitHub
- Owner: CatalaLang
- License: apache-2.0
- Language: OCaml
- Default Branch: master
- Size: 964 KB
Statistics
- Stars: 2
- Watchers: 4
- Forks: 1
- Open Issues: 11
- Releases: 6
Metadata Files
README.md
Catala VSCode extension and LSP server
Disclaimer
Be advised that this is a work in progress repository and is not yet considered as a fully functional VSCode extension.
Features
Client side:
- Syntax highlighting
LSP-server:
- Highlighting of miscellaneous type of errors
- Auto-completion
Getting started
Prerequisites
In order to build and use this extension, you will need to install:
Installation
VSCode Marketplace
The simplest way to install this extension is through the VSCode marketplace which is directly accessible in VScode. However, the extension still requires the Catala LSP server which, for the time being, need to be manually installed through OPAM using this command:
bash
opam pin catala-lsp git+https://github.com/CatalaLang/catala-language-server.git
-- and, optionally, you may also install the code formatter (see below).
Build from sources
It is also possible to build the extension from the sources through these commands:
```bash
1. Clone this repository
git clone https://github.com/CatalaLang/catala-language-server/
2. Enter the freshly created directory
cd catala-language-server/
3. Install the JS dependencies
npm install
4. Install the OCaml dependencies
opam install . --deps-only
5. Build the extension
npm run compile ```
From this point on, you may test the extension by skipping to the next section. Otherwise, you can package and install the extension in VSCode by following these extra steps:
```bash
1. Install VSCode extension CLI tool: e.g.,
sudo npm install -g @vscode/vsce
2. Package the extension
vsce package
3. Install the generated .vsix extension through the VSCode GUI or
by invoking:
code --install-extension catala-0.20.0.vsix ```
Testing
If you wish to test the extension without installing it, you may:
- Open VSCode at the repository's root (e.g., in a terminal
$ code .) - Go to "Run and Debug" in the VSCode sidebar (invoked by command "View: Show Run and Debug")
- Choose "Launch Client" and click on the play button
- A new VSCode window should open with the extension running
- you can press CTRL+R to reload the extension window to apply changes
Code formatting
catala-format is an
automated code formatting tool based on
topiary. To install
catala-format, use this command:
$ opam install catala-format
N.b. the installation may be lengthy as it needs to install topiary.
Once this is done, you may start (or reload) the extension and use the
format document command: Ctrl-p and type 'Format Document'. You may
also bind it to a handy keyboard shortcut. Beware: if the catala
program you are trying to format cannot be properly parsed, the
formatter call will fail.
catala-format can also be used as a standalone tool or plugged in
your favorite IDE. Type catala-format --help in a terminal for more
details.
Using the Custom Test Case Editor
The custom (visual) test case editor usage is controlled by a configuration setting. To enable or disable the custom editor:
- Open VSCode Settings (File > Preferences > Settings)
- Search for "Catala"
- Find the "Catala: Enable Custom Test Case Editor" setting
- Check or uncheck the box to enable or disable the custom test case editor
- Reload the VSCode window for the changes to take effect (you can do this by closing and reopening VSCode, or by running the "Developer: Reload Window" command from the Command Palette)
When the custom editor is disabled, test files will open in the default text editor.
Note: After changing the setting, you must reload the VSCode window for the changes to take effect. This is because the custom editor registration happens when the extension is activated, and changing the setting doesn't automatically re-register or unregister the editor.
Developing
When developing on the "front" (typescript side) of the extension, you may invoke
npm run watch to continuously build the extension.
License
All the code contained in this repository is released under the Apache license (version 2) unless another license is explicited for a sub-directory.
Release Process
This extension is automatically published to the VS Code Marketplace when a new GitHub release is created.
Creating a New Release
- Update Version in package.json:
- Update the version number in
package.json - Commit and push this change to the repository
- Create a GitHub Release:
- Go to the repository on GitHub and click on "Releases" in the right sidebar
- Click "Draft a new release"
- Create a new tag with the SAME version number as in package.json (e.g.,
v0.23.0or just0.23.0) - Add a title and release notes
- For pre-releases, check the "This is a pre-release" option
- For stable releases, leave the pre-release option unchecked
- Click "Publish release"
- Automated Process: The CI/CD workflow automatically:
- Verifies the release tag version matches package.json version
- Builds and packages the extension
- Publishes to VS Code Marketplace
- Attaches the VSIX file to the GitHub release
- Verification:
- Check GitHub Actions to monitor the workflow
- Verify the extension appears in the VS Code Marketplace
- Confirm the VSIX file is attached to the GitHub release
Owner
- Name: CatalaLang
- Login: CatalaLang
- Kind: organization
- Repositories: 4
- Profile: https://github.com/CatalaLang
GitHub Events
Total
- Create event: 71
- Release event: 4
- Issues event: 16
- Watch event: 4
- Delete event: 49
- Member event: 1
- Issue comment event: 27
- Push event: 262
- Pull request review comment event: 12
- Pull request review event: 49
- Pull request event: 108
Last Year
- Create event: 71
- Release event: 4
- Issues event: 16
- Watch event: 4
- Delete event: 49
- Member event: 1
- Issue comment event: 27
- Push event: 262
- Pull request review comment event: 12
- Pull request review event: 49
- Pull request event: 108
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 16
- Total pull requests: 151
- Average time to close issues: 13 days
- Average time to close pull requests: 3 days
- Total issue authors: 5
- Total pull request authors: 4
- Average comments per issue: 0.63
- Average comments per pull request: 0.4
- Merged pull requests: 123
- Bot issues: 0
- Bot pull requests: 2
Past Year
- Issues: 15
- Pull requests: 128
- Average time to close issues: 13 days
- Average time to close pull requests: 4 days
- Issue authors: 5
- Pull request authors: 4
- Average comments per issue: 0.67
- Average comments per pull request: 0.44
- Merged pull requests: 102
- Bot issues: 0
- Bot pull requests: 2
Top Authors
Issue Authors
- rprimet (10)
- vincent-botbol (3)
- denismerigoux (2)
- dev-perry (1)
- adelaett (1)
Pull Request Authors
- vincent-botbol (99)
- rprimet (61)
- AltGr (6)
- dependabot[bot] (2)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- 125 dependencies
- @types/mocha ^10.0.6 development
- @types/node ^18.11.18 development
- @types/vscode ^1.86.0 development
- eslint ^8.56.0 development
- typescript ^4.9.5 development
- tsc-watch ^6.2.0
- vscode-languageclient ^8.0.2
- actions/checkout v4 composite
- actions/setup-node v4 composite
- ocaml/setup-ocaml v3 composite