pytest-language-server 0.5.2__tar.gz → 0.7.0__tar.gz

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/.github/workflows/release.yml

@@ -244,6 +244,8 @@ jobs:
           sudo apt-get update
           sudo apt-get install -y gcc-aarch64-linux-gnu
       - name: Build binary
+        env:
+          CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER: aarch64-linux-gnu-gcc
         run: |
           cargo build --release --target ${{ matrix.target }}
       - name: Rename binary (Unix)
@@ -284,16 +286,16 @@ jobs:
           ls -lh
       - name: Install dependencies
         run: |
-          cd vscode-extension
+          cd extensions/vscode-extension
           npm install
           npm install -g @vscode/vsce
       - name: Package extension
         run: |
-          cd vscode-extension
+          cd extensions/vscode-extension
           vsce package
       - name: Publish to VSCode Marketplace
         run: |
-          cd vscode-extension
+          cd extensions/vscode-extension
           vsce publish -p ${{ secrets.VSCE_TOKEN }}
 
   publish-intellij:
@@ -341,43 +343,11 @@ jobs:
     name: Publish Zed extension
     runs-on: ubuntu-latest
     if: startsWith(github.ref, 'refs/tags/')
-    needs: [build-binaries]
     steps:
-      - uses: actions/checkout@v4
-      - name: Install Rust
-        uses: dtolnay/rust-toolchain@stable
-        with:
-          targets: wasm32-wasip1
-      - name: Download all binaries
-        uses: actions/download-artifact@v6
-        with:
-          pattern: binary-*
-          path: extensions/zed-extension/bin
-      - name: Flatten binaries
-        run: |
-          cd extensions/zed-extension/bin
-          find . -type f -name "pytest-language-server*" -exec mv {} . \;
-          find . -type d -empty -delete
-          chmod +x pytest-language-server-* || true
-          ls -lh
-      - name: Build Zed extension
-        run: |
-          cd zed-extension
-          cargo build --release --target wasm32-wasip1
-      - name: Package extension
-        run: |
-          cd zed-extension
-          mkdir -p dist
-          cp target/wasm32-wasip1/release/pytest_language_server.wasm dist/extension.wasm
-          cp -r bin dist/
-          cp extension.toml dist/
-      - name: Publish to Zed Extensions
-        run: |
-          cd zed-extension
-          # Note: Zed extension publishing requires manual submission or API key
-          # For now, just upload the packaged extension to GitHub releases
-          tar -czf ../pytest-language-server-zed-extension.tar.gz -C dist .
-      - name: Upload Zed extension to release
-        uses: softprops/action-gh-release@v2
+      - uses: huacnlee/zed-extension-action@v1
         with:
-          files: pytest-language-server-zed-extension.tar.gz
+          extension-name: pytest-language-server
+          extension-path: extensions/zed-extension
+          push-to: bellini666/extensions
+        env:
+          COMMITTER_TOKEN: ${{ secrets.COMMITTER_TOKEN }}

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/AGENTS.md

@@ -7,7 +7,7 @@ This document helps AI agents understand the pytest-language-server codebase str
 **pytest-language-server** is a Language Server Protocol (LSP) implementation for pytest fixtures, written in Rust. It provides IDE features like go-to-definition, find-references, and hover documentation for pytest fixtures.
 
 - **Language**: Rust (Edition 2021, MSRV 1.83)
-- **Lines of Code**: ~4,000 lines (2,501 in fixtures.rs, 1,574 in main.rs)
+- **Lines of Code**: ~3,050 lines (2,256 in fixtures.rs, 794 in main.rs)
 - **Architecture**: Async LSP server using tower-lsp
 - **Key Features**: Fixture go-to-definition, find-references, hover docs, fixture overriding, undeclared fixture diagnostics
 
@@ -18,8 +18,8 @@ This document helps AI agents understand the pytest-language-server codebase str
 ```
 src/
 ├── lib.rs          # Library exports (3 lines)
-├── main.rs         # LSP server implementation (~1,574 lines)
-└── fixtures.rs     # Fixture analysis engine (~2,501 lines)
+├── main.rs         # LSP server implementation (794 lines)
+└── fixtures.rs     # Fixture analysis engine (2,256 lines)
 ```
 
 ### Key Components
@@ -145,32 +145,37 @@ This is handled by `start_char` and `end_char` in `FixtureUsage`.
 ### Test Structure
 
 ```
+src/
+├── fixtures.rs           # Main code (2,256 lines)
+└── main.rs              # LSP server (794 lines)
+
 tests/
-├── test_project/         # Fixture test files for integration tests
-│   ├── conftest.py
-│   ├── test_example.py
-│   ├── test_parent_usage.py
-│   └── subdir/
-│       ├── conftest.py
-│       ├── test_hierarchy.py
-│       └── test_override.py
-└── test_parser_api.rs    # Integration tests
+├── test_fixtures.rs     # FixtureDatabase integration tests (60 tests, 2,951 lines)
+├── test_lsp.rs         # LSP protocol tests (13 tests, 1,187 lines)
+└── test_project/       # Fixture test files for integration tests
+    ├── conftest.py
+    ├── test_example.py
+    ├── test_parent_usage.py
+    └── subdir/
+        ├── conftest.py
+        ├── test_hierarchy.py
+        └── test_override.py
 ```
 
 ### Running Tests
 
 ```bash
-cargo test                    # Run all tests
-cargo test --lib             # Run library tests (fixtures.rs: 47 tests)
-cargo test --bin            # Run binary tests (main.rs: 13 tests)
-RUST_LOG=debug cargo test  # Run with debug logging
+cargo test                          # Run all tests (73 total)
+cargo test --test test_fixtures     # Run FixtureDatabase tests (60 tests)
+cargo test --test test_lsp         # Run LSP protocol tests (13 tests)
+RUST_LOG=debug cargo test          # Run with debug logging
 ```
 
 ### Test Coverage
 
-- **60 total tests passing** (as of v0.5.1)
-  - 47 tests in `src/fixtures.rs`
-  - 13 tests in `src/main.rs`
+- **73 total tests passing** (as of v0.6.0)
+  - 60 integration tests in `tests/test_fixtures.rs` (FixtureDatabase API)
+  - 13 integration tests in `tests/test_lsp.rs` (LSP protocol handlers)
 
 Key test areas:
 - Fixture definition extraction from various patterns

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/Cargo.lock

@@ -753,7 +753,7 @@ dependencies = [
 
 [[package]]
 name = "pytest-language-server"
-version = "0.5.2"
+version = "0.7.0"
 dependencies = [
  "dashmap 6.1.0",
  "rustpython-parser",

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "pytest-language-server"
-version = "0.5.2"
+version = "0.7.0"
 edition = "2021"
 rust-version = "1.83"
 authors = ["Thiago Bellini Ribeiro <hackedbellini@gmail.com>"]

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/EXTENSION_PUBLISHING.md

@@ -89,17 +89,44 @@ cd extensions/intellij-plugin
 
 ### 3. Zed Extension Setup
 
-**Note**: Zed currently uses a manual extension publishing process or requires submitting to their repository.
+**Automated Publishing (via GitHub Action):**
 
-**For Manual Distribution:**
-The CI automatically packages the Zed extension as `pytest-language-server-zed-extension.tar.gz` and uploads it to GitHub releases.
+Zed extensions are published by creating PRs to the official Zed extensions repository. This is automated using the `huacnlee/zed-extension-action` GitHub Action.
 
-**For Official Zed Extension Directory:**
-1. Fork https://github.com/zed-industries/extensions
-2. Add extension to `extensions/` directory
-3. Submit PR to Zed extensions repo
+**Setup Steps:**
 
-The extension will still be bundled with binaries in your GitHub releases for users to install manually.
+1. **Fork the Zed Extensions Repo:**
+   ```bash
+   # Go to https://github.com/zed-industries/extensions
+   # Click "Fork" (fork to your personal account, not an organization)
+   ```
+
+2. **Add Your Extension to Your Fork:**
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/extensions
+   cd extensions
+   git submodule add https://github.com/bellini666/pytest-language-server.git extensions/pytest-language-server
+   ```
+
+3. **Add Entry to extensions.toml:**
+   ```toml
+   [pytest-language-server]
+   submodule = "extensions/pytest-language-server"
+   path = "extensions/zed-extension"
+   version = "0.5.2"
+   ```
+
+4. **Create Initial PR:**
+   Submit the initial PR to zed-industries/extensions manually.
+
+5. **Automated Updates:**
+   After the initial setup, the GitHub Action automatically creates PRs to update your extension when you create a new release tag.
+
+**How It Works:**
+- When you push a new version tag (e.g., `v0.6.0`), the `publish-zed` job runs
+- It uses your `COMMITTER_TOKEN` to create a PR on your fork of zed-industries/extensions
+- The PR updates the submodule commit and version in `extensions.toml`
+- You review and merge the PR to your fork, then submit to zed-industries/extensions
 
 ### 4. GitHub Secrets Configuration
 
@@ -109,8 +136,17 @@ Add these secrets to your GitHub repository (Settings → Secrets and variables
 VSCE_TOKEN=<your-vscode-marketplace-token>
 JETBRAINS_TOKEN=<your-jetbrains-marketplace-token>
 CARGO_REGISTRY_TOKEN=<your-crates-io-token>
+COMMITTER_TOKEN=<your-github-pat-with-repo-and-workflow-scopes>
 ```
 
+**COMMITTER_TOKEN Setup (Required for Zed Extension):**
+1. Go to https://github.com/settings/tokens/new
+2. Create a **Classic** Personal Access Token with these scopes:
+   - `repo` (Full control of private repositories)
+   - `workflow` (Update GitHub Action workflows)
+3. Copy the token and add it as `COMMITTER_TOKEN` secret
+4. This token allows the Zed extension action to create PRs to your fork of zed-industries/extensions
+
 **Optional IntelliJ Plugin Signing (for paid plugins):**
 ```
 CERTIFICATE_CHAIN=<your-certificate-chain>
@@ -277,6 +313,10 @@ If versions get out of sync:
 - [ ] Create JetBrains plugin listing
 - [ ] Generate JetBrains token
 - [ ] Add JETBRAINS_TOKEN to GitHub secrets
+- [ ] Fork zed-industries/extensions repository
+- [ ] Generate GitHub PAT with repo & workflow scopes
+- [ ] Add COMMITTER_TOKEN to GitHub secrets
+- [ ] Add CARGO_REGISTRY_TOKEN to GitHub secrets
 - [ ] Test VSCode extension locally
 - [ ] Test IntelliJ plugin locally
 - [ ] Test Zed extension locally

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytest-language-server
-Version: 0.5.2
+Version: 0.7.0
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
@@ -47,7 +47,7 @@ A blazingly fast Language Server Protocol (LSP) implementation for pytest, built
 
 ![pytest-language-server demo](demo.gif)
 
-*Showcasing go-to-definition, find-references, hover documentation, and code actions. Demo also vibed into existence.* ✨
+*Showcasing go-to-definition, code completion, hover documentation, and code actions. Demo also vibed into existence.* ✨
 
 ## Features
 
@@ -58,6 +58,15 @@ Jump directly to fixture definitions from anywhere they're used:
 - Third-party fixtures from pytest plugins (pytest-mock, pytest-asyncio, etc.)
 - Respects pytest's fixture shadowing/priority rules
 
+### ✨ Code Completion
+Smart auto-completion for pytest fixtures:
+- **Context-aware**: Only triggers inside test functions and fixture functions
+- **Hierarchy-respecting**: Suggests fixtures based on pytest's priority rules (same file > conftest.py > third-party)
+- **Rich information**: Shows fixture source file and docstring
+- **No duplicates**: Automatically filters out shadowed fixtures
+- **Works everywhere**: Completions available in both function parameters and function bodies
+- Supports both sync and async functions
+
 ### 🔍 Find References
 Find all usages of a fixture across your entire test suite:
 - Works from fixture definitions or usage sites

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/README.md

@@ -21,7 +21,7 @@ A blazingly fast Language Server Protocol (LSP) implementation for pytest, built
 
 ![pytest-language-server demo](demo.gif)
 
-*Showcasing go-to-definition, find-references, hover documentation, and code actions. Demo also vibed into existence.* ✨
+*Showcasing go-to-definition, code completion, hover documentation, and code actions. Demo also vibed into existence.* ✨
 
 ## Features
 
@@ -32,6 +32,15 @@ Jump directly to fixture definitions from anywhere they're used:
 - Third-party fixtures from pytest plugins (pytest-mock, pytest-asyncio, etc.)
 - Respects pytest's fixture shadowing/priority rules
 
+### ✨ Code Completion
+Smart auto-completion for pytest fixtures:
+- **Context-aware**: Only triggers inside test functions and fixture functions
+- **Hierarchy-respecting**: Suggests fixtures based on pytest's priority rules (same file > conftest.py > third-party)
+- **Rich information**: Shows fixture source file and docstring
+- **No duplicates**: Automatically filters out shadowed fixtures
+- **Works everywhere**: Completions available in both function parameters and function bodies
+- Supports both sync and async functions
+
 ### 🔍 Find References
 Find all usages of a fixture across your entire test suite:
 - Works from fixture definitions or usage sites

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/demo.tape

@@ -13,10 +13,10 @@ Output demo.mp4
 
 Set Shell "bash"
 Set FontSize 12
-Set Width 1200
-Set Height 700
+Set Width 800
+Set Height 400
 Set Padding 10
-Set Framerate 20
+Set Framerate 30
 Set Theme "Dracula"
 
 Hide
@@ -24,9 +24,9 @@ Type "cd /Users/bellini/dev/pytest-language-server/tests/test_project" Enter
 Show
 
 # Title
-Type 'echo "pytest-language-server Demo"' Enter
+Type 'echo "🐍 pytest-language-server Demo ⚡"' Enter
 Sleep 1.5s
-Type 'echo "1. Hover Documentation"' Enter
+Type 'echo "📖 1. Hover Documentation & Go to Definition"' Enter
 Sleep 1.5s
 
 Type "nvim test_example.py" Enter
@@ -36,34 +36,59 @@ Hide
 Type ":set nu" Enter
 Show
 
+# Hover on sample_fixture (position cursor on the fixture name)
 Type "ggf(w"
 Sleep 1s
 Type "K"
-Sleep 3.5s
-Escape
+Sleep 3s
+
+# Go to definition (this will close hover and jump)
+Type "gd"
+Sleep 2.5s
+Ctrl+O
+Sleep 500ms
 
 Type "ZQ"
 Sleep 300ms
 
-Type 'echo "2. Go to Definition"' Enter
+Type 'echo "✨ 2. Code Completion"' Enter
 Sleep 1.5s
 
 Type "nvim test_example.py" Enter
-Sleep 2s
+Sleep 2.5s
 
 Hide
 Type ":set nu" Enter
 Show
 
-Type "ggf(w"
-Type "gd"
-Sleep 2.5s
+# Navigate to first test function and go to end of parameters
+Type "gg"
+Sleep 300ms
+Type "f)"
+Sleep 300ms
+Type "i, "
+Sleep 500ms
+
+# Trigger completion
+Ctrl+X
 Ctrl+O
+Sleep 2.5s
 
-Type "ZQ"
+# Navigate down in completion menu
+Down
+Sleep 500ms
+Down
+Sleep 500ms
+Enter
+Sleep 1.5s
+
+# Exit without saving
+Escape
+Sleep 300ms
+Type ":q!" Enter
 Sleep 300ms
 
-Type 'echo "3. Code Actions"' Enter
+Type 'echo "🔧 3. Code Actions (Quick Fixes)"' Enter
 Sleep 1.5s
 
 Type "nvim test_undeclared_example.py" Enter
@@ -86,6 +111,7 @@ Type ":9" Enter
 Sleep 2s
 
 Type "ZQ"
+Sleep 300ms
 
-Type 'echo "github.com/bellini666/pytest-language-server"' Enter
+Type 'echo "✨ github.com/bellini666/pytest-language-server ✨"' Enter
 Sleep 2s

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/extensions/intellij-plugin/build.sh

@@ -2,7 +2,10 @@
 # Simple build script for IntelliJ plugin without Gradle
 set -e
 
-echo "Building pytest-language-server IntelliJ plugin..."
+# Extract version from plugin.xml
+VERSION=$(grep -o '<version>[^<]*</version>' src/main/resources/META-INF/plugin.xml | sed 's/<version>\(.*\)<\/version>/\1/')
+
+echo "Building pytest-language-server IntelliJ plugin v${VERSION}..."
 
 # Clean previous builds
 rm -rf build
@@ -15,6 +18,13 @@ echo "Copying resources..."
 cp src/main/resources/META-INF/plugin.xml build/META-INF/
 cp src/main/resources/META-INF/pluginIcon.png build/META-INF/
 
+# Copy bundled binaries if they exist
+if [ -d "src/main/resources/bin" ] && [ -n "$(ls -A src/main/resources/bin 2>/dev/null)" ]; then
+  echo "Copying bundled binaries..."
+  mkdir -p build/bin
+  cp -r src/main/resources/bin/* build/bin/
+fi
+
 # Compile Kotlin files (simple compilation without dependencies for now)
 # Note: For a real LSP plugin, you'd need proper IntelliJ SDK compilation
 # For CI, we'll just package the source files which JetBrains can compile
@@ -24,7 +34,11 @@ cp -r src/main/java/com/github/bellini666/pytestlsp/*.kt build/classes/com/githu
 # Create JAR
 echo "Creating plugin JAR..."
 cd build
-jar cf ../pytest-language-server.jar META-INF/ classes/
+if [ -d "bin" ]; then
+  jar cf ../pytest-language-server.jar META-INF/ classes/ bin/
+else
+  jar cf ../pytest-language-server.jar META-INF/ classes/
+fi
 
 # Create distribution ZIP
 cd ..
@@ -33,7 +47,7 @@ cp pytest-language-server.jar dist/
 cd dist
 mkdir -p pytest-language-server/lib
 mv pytest-language-server.jar pytest-language-server/lib/
-zip -r pytest-language-server-0.5.1.zip pytest-language-server/
+zip -r pytest-language-server-${VERSION}.zip pytest-language-server/
 
-echo "✓ Plugin built successfully: dist/pytest-language-server-0.5.1.zip"
-ls -lh pytest-language-server-0.5.1.zip
+echo "✓ Plugin built successfully: dist/pytest-language-server-${VERSION}.zip"
+ls -lh pytest-language-server-${VERSION}.zip

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/extensions/intellij-plugin/src/main/resources/META-INF/plugin.xml

@@ -1,7 +1,7 @@
 <idea-plugin>
     <id>com.github.bellini666.pytest-language-server</id>
     <name>pytest Language Server</name>
-    <version>0.5.2</version>
+    <version>0.7.0</version>
     <vendor email="hackedbellini@gmail.com" url="https://github.com/bellini666/pytest-language-server">Thiago Bellini Ribeiro</vendor>
 
     <description><![CDATA[

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/extensions/vscode-extension/.vscodeignore

@@ -12,3 +12,6 @@ node_modules/**
 out/**
 .eslintrc.json
 tsconfig.json
+
+# Include bundled binaries
+!bin/**

pytest_language_server-0.7.0/extensions/vscode-extension/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Patrick Arminio
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/extensions/vscode-extension/package.json

@@ -2,7 +2,7 @@
   "name": "pytest-language-server",
   "displayName": "pytest Language Server",
   "description": "A blazingly fast Language Server Protocol implementation for pytest fixtures",
-  "version": "0.5.2",
+  "version": "0.7.0",
   "publisher": "bellini666",
   "license": "MIT",
   "author": "Thiago Bellini Ribeiro <hackedbellini@gmail.com>",

{pytest_language_server-0.5.2 → pytest_language_server-0.7.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "pytest-language-server"
-version = "0.5.2"
+version = "0.7.0"
 description = "A blazingly fast Language Server Protocol implementation for pytest"
 authors = [{name = "Thiago Bellini Ribeiro", email = "hackedbellini@gmail.com"}]
 readme = "README.md"