Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: liquid-java/vscode-liquidjava
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: liquid-java/vscode-liquidjava
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: feat/155-state-errors-in-view
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 21 files changed
  • 3 contributors

Commits on Oct 25, 2026

  1. Keep the state error in the State Machine view and link it to the editor

    The tab keeps the last state error shown and follows the error at the cursor,
    steps through several errors, counts them on the tab, and links back to the
    error in the Verification tab. State errors get a labelled Show in state
    machine button and CodeLens.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
    CatarinaGamboa and claude committed Oct 25, 2026
    Configuration menu
    Copy the full SHA
    79accc2 View commit details
    Browse the repository at this point in the history
  2. Open the State Machine view on the first state error of the file

    Count only the state errors of the current file, keep the focus toggle with
    the legend apart from View error, and move Show in state machine to the top
    of the error.
    
    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
    CatarinaGamboa and claude committed Oct 25, 2026
    Configuration menu
    Copy the full SHA
    f3e6eba View commit details
    Browse the repository at this point in the history
  3. Use the verifier's error context in the state error test fixtures

    Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
    CatarinaGamboa and claude committed Oct 25, 2026
    Configuration menu
    Copy the full SHA
    9fc9be9 View commit details
    Browse the repository at this point in the history

Commits on Oct 26, 2026

  1. Put the State Machine tab next to Verification (#162)

    ## Description
    Stacked on #159; merge that first. Independent of #161.
    
    The tabs are now **Verification · State Machine · Context**.
    Verification and State Machine link to each other through **Show in
    state machine** and **View error**, so they now sit side by side.
    Context shows the variables at the cursor for any file and works fine at
    the end.
    
    The walkthrough steps and the README sentence that lists them follow the
    same order.
    
    ## Screenshots
    `E_OSS_A1_19_AccessKeyGenerator` from the C-stars proposal in
    building-examples-liquidjava.
    
    **Before**
    
    <img width="560" alt="Tabs: Verification, Context, State Machine"
    src="https://raw.githubusercontent.com/liquid-java/vscode-liquidjava/pr-screenshots/tab-order/before.png"
    />
    
    **After**
    
    <img width="560" alt="Tabs: Verification, State Machine, Context"
    src="https://raw.githubusercontent.com/liquid-java/vscode-liquidjava/pr-screenshots/tab-order/after.png"
    />
    
    ## Tests
    - `npm run lint` and `npm run test:typecheck`: clean.
    - `npm run test:unit`: 90 passed. New test in `script.spec.ts` for the
    tab order.
    - `npm test` (VS Code): passed; the walkthrough test now expects the new
    step order.
    - Server `mvn test` and the local smoke test: passed.
    
    🤖 Generated with [Claude Code](https://claude.com/claude-code)
    
    Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
    CatarinaGamboa and claude authored Oct 26, 2026
    Configuration menu
    Copy the full SHA
    5b65c2c View commit details
    Browse the repository at this point in the history
Loading