-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Feature request: Expose types of snippet globals for nicer development #1025
Comments
Related #378 (but incomplete) |
Oh yeah, for sure!
I'd honestly be fine with either option since I don't really anticipate many major additions to luasnip, so the additional long-time-work induced by the first option may not outweigh one-time work and complexity introduced by the second one (though the second one may be fun to figure out) Unfortunately, I really don't use annotations at all though, so my motivation for doing either is pretty low 😅 |
Only that it's marked as draft, and adding annotations for a small number of api-functions only seemed a bit weird. |
Sounds good. I think that splitting the work into smaller PRs will be less overwhelming than documenting the entire API at once (I think no one has the motivation for that hehe). I’m also happy to help with this btw! |
Ah, yeah, probably also true :D
Yay, hoped for just that :P |
Hi, I am also interested in this. Since the other PR is merged. Is there anything else blocking this? |
When writing custom snippets, it would be really helpful to use type annotations for
s
,t
, and other global snippet constructors for better editing support :)The text was updated successfully, but these errors were encountered: