🤔 What's the problem you're trying to solve?
I may be missing a way to achieve this now, apologies if so. It would be super helpful if there was a way for us to configure custom treesitter queries for the language service to use when finding step definitions, as the most-recent hard-coded options are slightly different from the current structure I am working with (that unfortunately I cannot change), causing 0 steps to be found in all glue files.
✨ What's your proposed solution?
Add an additional setting that allows for adding custom treesitter syntax queries, enabling much more flexibility for developers working on non-standard step definition structure.
⛏ Have you considered any alternatives or workarounds?
Considered cloning the language service and patching the local install of the language server.
📚 Any additional context?
No response
🤔 What's the problem you're trying to solve?
I may be missing a way to achieve this now, apologies if so. It would be super helpful if there was a way for us to configure custom treesitter queries for the language service to use when finding step definitions, as the most-recent hard-coded options are slightly different from the current structure I am working with (that unfortunately I cannot change), causing 0 steps to be found in all glue files.
✨ What's your proposed solution?
Add an additional setting that allows for adding custom treesitter syntax queries, enabling much more flexibility for developers working on non-standard step definition structure.
⛏ Have you considered any alternatives or workarounds?
Considered cloning the language service and patching the local install of the language server.
📚 Any additional context?
No response