fix: non-function import expression syntax highlighting

[alehechka]

Overview

This is a follow-up to #38 from a recommendation in a-h/templ#566. This adds support for syntax highlighting on non-function components such as the following:

templ higherOrderTemplate(a, b templ.Component) {
	<div class="left">
		@a
	</div>
	<div class="right">
		@b
	</div>
}

Before

After

Caveat

However, since this is reusing the current import-expression pattern it passes the function name into source.go which marks the syntax as a variable instead of a function since it doesn't have an open parenthesis. Just wanted to point this out to make sure this is okay or if we'd like to override this scenario to force the function syntax token?

[joerdav]

Had a quick look, this looks good. A side note though, what is it you're using for the textmate debugs?

[alehechka]

A side note though, what is it you're using for the textmate debugs?

@joerdav that's the VSCode built-in inspector, to start it open the command pallet and run Developer: Inspect Editor Tokens and Scopes.

[alehechka]

@joerdav before you ship the next version of the extension can you check out #35?

It's adding an important fix to inline script tags. I left one comment to also fix inline style tags and would love to see both of those fixed for the next release.

[joerdav]

That's a useful command, thanks!

Yes will take a look at that first.

[joerdav]

On the caveat, I think that's acceptable, no need to override form my understanding.