Closed sunscreem closed 2 years ago
The Antlers completions will normally only get triggered when inside {{ }}
regions. Outside of those areas, the HTML/CSS/etc suggestions take over :)
Thanks John.
It's not working inside in the {{ }}
. The problem is I'm an idiot and took the screen grab incorrectly - sorry about that. Here's a better one. I was expecting to see it suggest partial
? Maybe I'm not understanding the plug in?
It should work like how you have it (sometimes it doesn't place nice with Emmet, though) - does the language in the bottom right corner of VS Code say HTML (Statamic Antlers)
?
It does John yes:
Sorry - badly cropped.
No worries; thanks for checking!
Seems like we are getting closer to bug territory - could you send your install's emmet configuration, as well as a list of all installed VS Code extensions?
Thank you!
Sorry for the delay @JohnathonKoster
Emmet Config (from settings.json):
"emmet.triggerExpansionOnTab": true,
"emmet.includeLanguages": {
"javascript": "javascriptreact",
"vue-html": "html",
"twig": "html",
"razor": "html",
"plaintext": "jade",
"vue": "vue"
},
"tailwindCSS.emmetCompletions": true,
Can you try uninstalling the ahdesign.language-antlers@0.1.0 extension and restarting VS Code?
The two extensions are not compatible with each other, and that one may prevent the required language client from starting.
@JohnathonKoster Sorry for the crazy slow reply on this. I think I have it working now.
I turned on verbose logging with the antlers language server and noticed references to liquid!? I disabled any extensions I've been using for shopify development and it now seems to be playing ball.
If I type {{ partial:
for example its offers to autocomplete :)
I also not it created a .antlers.json
file now.
I've installed the plug in, restarted VS code and its generated an .antlers.json file and added some files to storage.
In my templates though I'm not seeing anything different:
If I turn on the logging I can see things happening as I type:
99% chance I'm being dumb here.
I use a remote workspace (via ssh). Could that be the issue?