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

feat(lsp): Arguments to explainError/renderDiagnostic from current line #431

Merged
merged 14 commits into from
Jun 21, 2024
Merged

feat(lsp): Arguments to explainError/renderDiagnostic from current line #431

merged 14 commits into from
Jun 21, 2024

Conversation

Rumi152
Copy link
Contributor

@Rumi152 Rumi152 commented Jun 19, 2024

feat(lsp): explainError and renderDiagnostic command now have optional argument {cycle?|current?}. It default to cycle which is current behavior, current option makes it search for diagnostic only in the current cursor line

Copy link
Contributor

Review Checklist

Does this PR follow the Contribution Guidelines? Following is a partial checklist:

Proper conventional commit scoping:

  • For example, fix(lsp): some lsp-related bugfix

  • Pull request title has the appropriate conventional commit prefix.

If applicable:

  • Tested
    • Tests have been added.
    • Tested manually (Steps to reproduce in PR description).
  • Updated documentation.
  • Updated CHANGELOG.md

@Rumi152 Rumi152 marked this pull request as draft June 19, 2024 19:26
@Rumi152 Rumi152 changed the title Arguments to explainError/renderDiagnostic from current line feat(lsp): Arguments to explainError/renderDiagnostic from current line Jun 19, 2024
@Rumi152
Copy link
Contributor Author

Rumi152 commented Jun 19, 2024

Its my first more serious pull request so I'm sorry if I did something wrong, I don't know how to install nix on windows

@Rumi152 Rumi152 marked this pull request as ready for review June 19, 2024 19:45
@Rumi152
Copy link
Contributor Author

Rumi152 commented Jun 19, 2024

#429

@mrcjkb
Copy link
Owner

mrcjkb commented Jun 19, 2024

Hey, thanks for the contribution. 🙏
This is definitely a great idea!

I'm quite busy at the moment but I'll make sure to give it a review and a test drive in the next few days 😃

CHANGELOG.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
lua/rustaceanvim/commands/diagnostic.lua Outdated Show resolved Hide resolved
lua/rustaceanvim/init.lua Outdated Show resolved Hide resolved
@mrcjkb
Copy link
Owner

mrcjkb commented Jun 21, 2024

CI is failing because stylua needs to be run.

@Rumi152 Rumi152 requested a review from mrcjkb June 21, 2024 15:36
CHANGELOG.md Outdated Show resolved Hide resolved
@Rumi152 Rumi152 requested a review from mrcjkb June 21, 2024 16:14
Copy link
Owner

@mrcjkb mrcjkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stylua is still failing :(

@Rumi152
Copy link
Contributor Author

Rumi152 commented Jun 21, 2024

I'll try to figure it out

@Rumi152
Copy link
Contributor Author

Rumi152 commented Jun 21, 2024

I think it should work now

CHANGELOG.md Outdated Show resolved Hide resolved
@mrcjkb mrcjkb merged commit 34fb2b4 into mrcjkb:master Jun 21, 2024
5 checks passed
@Rumi152
Copy link
Contributor Author

Rumi152 commented Jun 21, 2024

Sorry for all the headache I've caused and thanks for this great plugin 😄

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.

2 participants