Fix HurlRunnterToEntry using treesitter (#116)

jellydn / hurl.nvim

Hurl.nvim is a Neovim plugin designed to run HTTP requests directly from `.hurl` files. Elevate your API development workflow by executing and viewing responses without leaving your editor.

https://gyazo.com/19492e8b5366cec3f22d5fd97a63f37a

MIT License

148 stars 15 forks source link

Fix HurlRunnterToEntry using treesitter (#116) #125

Closed jellydn closed 5 months ago

jellydn commented 5 months ago

Fix HurlRunnterToEntry using treesitter
chore(doc): auto generate docs
Fix find entry method returing two nodes range.

Lua index starts on 1 so we were accidentally returing the line range of the current node plus one line of the next node.

[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Co-authored-by: github-actions[bot] github-actions[bot]@users.noreply.github.com Co-authored-by: pre-commit-ci[bot] 66853113+pre-commit-ci[bot]@users.noreply.github.com## WHAT

WHY

HOW

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Linter
[ ] Tests
[ ] Review comments
[ ] Security

changeset-bot[bot] commented 5 months ago

⚠️ No Changeset found

Latest commit: bc58235713012b9da93ee4c4aa06f4b685bae274

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

sweep-ai[bot] commented 5 months ago

Apply Sweep Rules to your PR?

[ ] Apply: All docstrings and comments should be up to date.
[ ] Apply: Commit messages should be descriptive and provide a clear explanation of the changes made.
[ ] Apply: Author names should be consistent and use proper formatting.
[ ] Apply: Code should be properly formatted and follow a consistent style guide.
[ ] Apply: There should be no unnecessary whitespace or trailing spaces in the code.
[ ] Apply: Variable and function names should be meaningful and descriptive.

This is an automated message generated by Sweep AI.