You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your request. It looks like a lot of work, and also to run against the spirit of srgn a bit. The "prepared queries" are a large part of what makes srgn useful in my mind, and with a pluggable aka custom language, they couldn't be offered anymore. At that point, using tools like ast-grep or the tree-sitter CLI directly seems like suitable solutions.
Hi Alex!
Thanks for srgn!
The motivation for this issue was, that in ast-grep you can't (like in srgn) use “tree-sitter queries” to select matches. If you don't write grammars, that is probably not an issue, but if you want to customize the tooling for a language, you have to remember two queries: The tree-sitter query and the query used, e.g., in ast-grep. That's in my view the main advantage of srgn over ast-grep, but this advantage mainly is important, if you are familiar with the tree-sitter queries, e.g., you most likely wrote or modified your own custom grammar. So even for a subset of features of srgn custom language support might be motivated?
Or, as you mentioned, using tree-sitter directly in your scripts.
Hi!
Please add Custom Language Support.
Thanks!
The text was updated successfully, but these errors were encountered: