Add support for the schema tag

[eloyesp]

Implement the changes from #16 to have syntax highlighting on section schema.

[tpope]

Been on the fence about this proprietary extension but I guess it's been requested enough that I'll go for it. Let's rename the group to @liquidJson.

[eloyesp]

May be we can add this conditionally, only when the file matches "sections/*.liquid" making something like a subtype, but I'm not sure how to implement that and not sure if it's worth the effort. There are other two special tags for JavaScript and stylesheet that, while are not as important (rarely used), could also have special syntax highlighting. Just mention to check your thoughts on those ideas...

[tpope]

Wrap those in a if b:liquid_subtype ==# 'html' and it's probably fine, as CSS and JavaScript syntax highlighting already gets indirectly loaded in that case anyways. Are they also Shopify specific?

[eloyesp]

Just wanted to note that I've not forgot about this, but have problems finding the time... will work on this ASAP :)

[eloyesp]

Ok it is working.

I were trying to make matchit work, but it seems that I'm missing something, it does work with if, for, etc, but not with capture or style or schema.

Also, the indentation of JSON or CSS sections does not work and could not make it work as expected (using =).

[tpope]

Is this what you're missing?

vim-liquid/ftplugin/liquid.vim

Line 56 in dd5243a

let b:match_words .= '\<\%(if\w*\|unless\|case\)\>:\<\%(elsif\|else\|when\)\>:\<end\%(if\w*\|unless\|case\)\>,\<\%(for\|tablerow\)\>:\%({%\s*\)\@<=empty\>:\<end\%(for\|tablerow\)\>,<\(capture\|comment\|highlight\)\>:\<end\1\>'

[eloyesp]

Yes, but I could not get it working... (Even the capture:endcapture is not working... )

[tpope]

Looks like a \ was missing. I fixed it.

[tpope]

This variable is not guaranteed to be defined. Use if get(b:, 'liquid_subtype', 'html') ==# 'html'.

[eloyesp]

Ok, I've added a exists('b:liquid_subtype') check instead mainly because it is already on the code (but also because it's easier to understand). I can correct if it is wrong.

[tpope]

That's a behavior change: My version is true when b:liquid_subtype is undefined and yours is false. But I think your behavior is probably the more sensible one? Leave what you have for now.

[tpope]

I think keywords like schema should be highlighted. This can be implemented the same way as highlight, although untangling how that works might take a bit of doing thanks to the use of :execute.

(Notably, raw and comment are not currently highlighted. I believe my rationale was that these commands don't actually "do" anything, which is a dubious justification and was probably a mistake.)

[eloyesp]

I could not make the schema, endschema, style and endstyle keywords to be highlighted as liquidKeywords, using matchgroup makes the highlight use a single color for the {%- and for the keyword itself, and I cannot make the region skip the start and end itself. Using offsets and crazy patterns should do the trick, but I could not make it work.

Any help is appreciated, I've been fighting with this a lot.