L3MON4D3

Mhmmm interesting idea :+1: I definitely like defining properties of the function (position of the `opts`-arg, how can it be overridden) close to the function, as opposed to in a...

> > To implement this, we'd have to turn all outward-facing functions into tables with __call, right? > > Crap, I forgot functions are not indexable in lua :face_exhaling: xD...

Oho, I use Python sometimes but have never seen that, cool

Okay, works pretty well, I've renamed everything to reflect that we're extending, not overriding the passed args (not sure what's easier to understand, overriding defaults or extending passed arguments...) Here's...

Ahh, yeah, that file is so small it's fine to re-export :+1: Can you think of useful functions to extend? I guess * node-constructors (not thaaaaaaat useful, but one can...

@leiserfg Would you take a look?

Hell yeah, that's what I wanna hear :D Thank you!

I'm not familiar at all with react, but I'll assume that `useEffect` is a function defined in a module not imported by default, and when completing, choosing the plain-text `useEffect()`...

Well, we already support - lua callbacks on snippet enter (register per-snippet) - reading from a `luasnip`-field in the json (used currently for auto-triggered snippets) The only piece that's somewhat...

I think we can try adding some luasnip-specific stuff to `friendly-snippets` via PR, if they don't like it, we can still fork