Skip to content

Add CSS/HTML syntax highlighting in tagged template strings #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

deathaxe
Copy link
Contributor

@deathaxe deathaxe commented Jun 4, 2025

This PR adds syntax highlighting in css`...` and html`...` tagged template strings.

It requires CSS syntax of ST4180+ and is therefore not compatible with earlier builds.

It also fixes an issue with {{ ... }} not being properly detected in more recent ST builds.

A related core fix sublimehq/Packages#4055 is deployed with ST4193+.

Most important parts are backported to CSS (for Ngx) syntax to maintain compatibility with ST4180.

@deathaxe deathaxe force-pushed the feat/tagged-template-highlighting branch 2 times, most recently from eade676 to fc3043b Compare June 4, 2025 13:26
This commit adds syntax highlighting in `` css`...` `` and `` html`...` ``
tagged template strings.
@deathaxe deathaxe force-pushed the feat/tagged-template-highlighting branch from fc3043b to 02e7524 Compare June 4, 2025 13:30
@princemaple princemaple merged commit 6947919 into princemaple:main Jun 4, 2025
1 check passed
@princemaple
Copy link
Owner

Getting really complex. Never expected template syntax highlighting to get to this level 😂

@deathaxe deathaxe deleted the feat/tagged-template-highlighting branch June 4, 2025 14:02
@deathaxe
Copy link
Contributor Author

deathaxe commented Jun 4, 2025

Indeed.

@deathaxe
Copy link
Contributor Author

deathaxe commented Jun 4, 2025

v1.2.0 shouldn't have been released before wbond/package_control_channel#9127 is merged.

This will probably break syntax highlighting for those still using ST4152..4179.

@princemaple
Copy link
Owner

My bad. I woke up and deleted the release and tag but apparently it was picked up half an hour ago. Would people simply fail to upgrade?

@princemaple
Copy link
Owner

Looks like PC picked up the change. Hopefully if someone did picked up 1.2 but shouldn't, they could just fix it by re-installing.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants