Conversation
Reorganize the VSCode language client extension into its own ./jetls-client directory to better separate concerns between the language server (JETLS.jl) and the VSCode client extension. Changes: - Move all extension files to ./jetls-client/ directory - Split CHANGELOG.md: JETLS.jl changes remain in root, jetls-client history moved to jetls-client/CHANGELOG.md - Add comprehensive jetls-client/README.md with installation, configuration, and usage documentation based on docs/src/index.md - Add jetls-client development section to DEVELOPMENT.md - Update package.json metadata: - Add repository.directory field for monorepo structure - Add homepage pointing to jetls-client/README.md - Add bugs URL for issue tracking - Add 'clean' npm script - Add GitHub Actions workflow for jetls-client CI (runs npm run check) - Update root README.md with license section This structure aligns with standard monorepo practices and makes the extension easier to maintain, test, and publish independently.
Move the .vscode directory containing VSCode extension development configurations (launch.json, tasks.json, etc.) into the jetls-client directory, as these are specific to jetls-client extension development.
Update jetls-client to v0.2.0 with enhanced update notification system that
guides users through the breaking changes in JETLS installation method.
Changes:
- Update CHANGELOG.md with v0.2.0 release notes including breaking changes
and installation steps
- Implement three-tier notification system in checkForUpdates():
1. First-time installation: Welcome message with 'Install JETLS' button
that runs the new installation command
2. v0.1.x -> v0.2.0 upgrade: Warning message about breaking changes with
'Reinstall JETLS' button and link to migration guide (CHANGELOG.md#v020)
3. Normal updates: Standard update notification with 'Update JETLS' button
- All notifications provide direct terminal commands or documentation links
for easy user action
The v0.2.0 release requires users to reinstall JETLS using the new
`jetls` executable app method instead of the previous runserver.jl approach.
The notification system ensures smooth migration for existing users while
providing clear onboarding for new users.
Separates LSP testing into its own workflow file and adds path-based triggers to all workflows to avoid unnecessary runs.
The VSCode-specific communication channel configuration was documented in both docs/src/launching.md and jetls-client/README.md. This consolidates the documentation by: - Removing the VSCode-specific section from docs/src/launching.md - Expanding jetls-client/README.md with detailed channel selection documentation, including automatic environment detection and manual override options This improves maintainability by keeping VSCode-specific settings in the extension's README while the main documentation focuses on the general jetls executable behavior.
Vendored packages' weakdeps can interact with user's package environment unexpectedly. This change removes weakdeps and extensions that are not actually used when JETLS is loaded. For extensions that are used (i.e., their trigger packages are loaded), the weakdep UUIDs are updated to the vendored versions to ensure proper resolution. Written by Claude
Update DEVELOPMENT.md to reflect the new release workflow: - Release branches use `releases/YYYY-MM-DD` naming convention - Branches are created from `release`, merged with `master`, then vendored - Release branches must be kept as they are referenced by `[sources]` - Add documentation for `--local` flag for local testing Written by Claude
When not using --local, the [sources] entries reference the current branch which hasn't been pushed yet, causing Pkg.instantiate() to fail with "Did not find rev". Only run Pkg.instantiate() in --local mode where path references are used. Written by Claude
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.