Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: cdot parser error message range #4528

Merged
merged 2 commits into from
Jun 21, 2024
Merged

fix: cdot parser error message range #4528

merged 2 commits into from
Jun 21, 2024

Commits on Jun 21, 2024

  1. fix: cdot parser error message range 

    as #4527 describes there is inconsistency between `by`, `case` and
`next` on the one hand who, if the goal isn’t closed, put squiggly
underlines on the first line, and `.`, which so far only squiggled the
dot (which is a very short symbol!)

With this change the same mechanism as used by `case`, namely
`withCaseRef`, is also used for `.`.
    @nomeata
    nomeata committed Jun 21, 2024
    Configuration menu
    Copy the full SHA
    ded4f53 View commit details
    Browse the repository at this point in the history

  2. Update tests

    @nomeata
    nomeata committed Jun 21, 2024
    Configuration menu
    Copy the full SHA
    018090e View commit details
    Browse the repository at this point in the history