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.

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

[LSP] Exclude repl output from lsp #1479

Merged
merged 1 commit into from
Jan 21, 2022

Conversation

ericdallo
Copy link
Contributor

What has Changed?

  • Never send repl content to LSP analysis

Fixes #1250

My Calva PR Checklist

I have:

  • Read How to Contribute.
  • Directed this pull request at the dev branch. (Or have specific reasons to target some other branch.)
  • Made sure I have changed the PR base branch, so that it is not published. (Sorry for the nagging.)
  • Updated the [Unreleased] entry in CHANGELOG.md, linking the issue(s) that the PR is addressing.
  • Figured if anything about the fix warrants tests on Mac/Linux/Windows/Remote/Whatever, and either tested it there if so, or mentioned it in the PR.
  • Added to or updated docs in this branch, if appropriate
  • Tests
    • Tested the particular change
    • Figured if the change might have some side effects and tested those as well.
    • Smoke tested the extension as such.
    • Tested the VSIX built from the PR (so, after you've submitted the PR). You'll find the artifacts by clicking Show all checks in the CI section of the PR page, and then Details on the ci/circleci: build test.
  • Referenced the issue I am fixing/addressing in a commit message for the pull request.
    • If I am fixing the issue, I have used GitHub's fixes/closes syntax
    • If I am fixing just part of the issue, I have just referenced it w/o any of the "fixes” keywords.
  • Created the issue I am fixing/addressing, if it was not present.

Ping @PEZ, @bpringe

src/lsp/main.ts Outdated Show resolved Hide resolved
@PEZ
Copy link
Collaborator

PEZ commented Jan 18, 2022

Thanks!

@PEZ
Copy link
Collaborator

PEZ commented Jan 18, 2022

There seems to be some unrelated commits in the PR branch. Can you clean that up? (I'm not sure this is necessary, but it is generally easier to deal with ”clean” PRs 😄.)

@PEZ
Copy link
Collaborator

PEZ commented Jan 18, 2022

@bpringe Are we relying on clojure-lsp in a way that we need to consider before merging this? I seem to recall something about the debugger using clojure-lsp analysis.

@ericdallo ericdallo force-pushed the exclude-repl-from-lsp branch from 2210547 to 72d4d53 Compare January 18, 2022 12:25
@ericdallo
Copy link
Contributor Author

Thanks @PEZ ! Done, LMK if any more issues

@bpringe
Copy link
Member

bpringe commented Jan 21, 2022

@PEZ The debugging code just uses clojure-lsp for decorations (for the instrumented functions). It doesn't seem to even add decorations in the repl window currently, and I'm unsure if that's intentional, but either way, I don't think it matters if this disallows that.

@bpringe
Copy link
Member

bpringe commented Jan 21, 2022

Thanks @ericdallo! Let's merge. 🚀

@bpringe bpringe merged commit e44cf03 into BetterThanTomorrow:dev Jan 21, 2022
@bpringe
Copy link
Member

bpringe commented Jan 21, 2022

By the way, I removed that newline between changes in the unreleased section of the changelog (on dev). It might have caused an issue with our publish script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants