Pokey Rule
Pokey Rule
> This is ESLint autofixable, so will show up as a quick fix in VSCode. Ah no I don't mean once it's already imported. I mean if you have a...
@auscompgeek I'm curious why you closed this one. I'm overall supportive of this direction, modulo the questions above
I think basically it would involve just pulling this branch, then trying to do an auto-import and see what happens. But I agree this rule probably isn't a massive win...
I think you definitely want this kind of functionality when you're in a list-valued snippet hole, to indicate you'd like to create another element of the list, which would then...
I don't think we're actually too far off. On the insert snippet PR we can already specify the default insertion scope for a snippet, so that eg "snip foo after...
I'd be inclined to restrict that kinda thing to nested snippets in list-valued snippet holes at the start and see if that gets us what we need
> Also a question about your edit. The 'before' and 'after' commands seem to be working as written. Is this just a default term that has changed? Huh yeah I...
> @pokey Are we still maintaining the original cheatsheet? Not really. Hoping to remove it soon
Ah right. Is there any reason we want that to be open, or is the fix as easy as just making it closed?
🤷 I'd be tempted to just change it and see if any tests break