Fix HurlRunnterToEntry using treesitter

[hsanson]

WHAT

Modify HurlRunnerToEntry to work using treesitter parser. This allows to run to a specific entry without having to be exactly located at the start of the entry where the verb is located.

WHY

HOW

Screenshots (if appropriate):

Types of changes

• [x] 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]]

⚠️ No Changeset found

Latest commit: ab9977987831fbfe06868711aad30a71a26329c1

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.

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]]

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.

[jellydn]

Thanks. I will take a try tonight.

[jellydn]

FYI - Just synced your change to https://github.com/jellydn/hurl.nvim/tree/canary and the PR is not working properly yet.

[hsanson]

FYI - Just synced your change to https://github.com/jellydn/hurl.nvim/tree/canary and the PR is not working properly yet.

Please let me know what issues you are experiencing and if possible a sample hurl file to reproduce them. I have tested it on my hurl files and seems to work properly.

[jellydn]

FYI - Just synced your change to canary and the PR is not working properly yet.

Please let me know what issues you are experiencing and if possible a sample hurl file to reproduce them. I have tested it on my hurl files and seems to work properly.

Sure, I will push my test file to repository so you could try as well.

[jellydn]

Hi @hsanson Here is the simple test file https://github.com/jellydn/hurl.nvim/commit/ae57eba85eafd80d54c1f10c2d212383e8e55389 It works with main but not working properly with canary branch.

[jellydn]

Just FYI - I've reverted to using the find verb instead of treesitter parser.

Reproduce:

• Checkout canary, open example.hurl
• Place cursor at line 1, then run HurlRunnerAt

The canary branch will return the Google response instead of manga API. @hsanson

[jellydn]

Canary:

Main:

[hsanson]

@jellydn sorry for the issue... please test if this fixes it for you:

• https://github.com/jellydn/hurl.nvim/pull/124

[jellydn]

Thanks @hsanson Almost there. The parser logic will failed if there is a comment on hurl, e.g: https://github.com/jellydn/hurl.nvim/commit/9f773eff4a061d7d5e66a1c58af345dc365b6417

[jellydn]

For now, this is my solution :) https://github.com/jellydn/hurl.nvim/commit/4d4e4ff9df020522dca8a6dc9ea7fd3dfa25069d

[hsanson]

@jellydn simple solution and seems to work as far as I can see... thanks. Better than trying to fix the treesitter parser that does not seem to properly parse the comments and treat them as errors. Specially the top most comment.

You can see how the treesitter sees the file using :InspectTree. This is a very useful tool to understand hurl grammar.

[jellydn]

Great. Thanks, @hsanson Also, the treesitter parser only works for nightly. I will bring the find verb back to fallback on stable version.

[jellydn]

FYI https://github.com/jellydn/hurl.nvim/commit/c10a905