Skip to content

Conversation

@lachrist
Copy link

@lachrist lachrist commented May 27, 2025

Scope syntax coloring to Juviх by consistently adding a .juvix suffix to both regular and semantic token types.

Fixes #160

Fix the overly broad scope configuration that causes the extension to affect non-semantic syntax coloring across all languages.

anoma#160
@lukaszcz lukaszcz self-requested a review May 27, 2025 11:27
package.json Outdated
"module.juvix"
],
"number": [
"numeric.juvix"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be number.juvix, as used in other places?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, I can confirm that numbers are highlighted correctly now.

@lukaszcz
Copy link
Contributor

Thanks for this PR! We didn't notice the issue before.

@lachrist lachrist force-pushed the scope-syntax-coloring branch from d21f0ee to 469d1a6 Compare May 27, 2025 12:55
Fix the overly broad scope configuration that causes the extension to affect semantic syntax coloring across all languages.

anoma#160
@lachrist lachrist force-pushed the scope-syntax-coloring branch from 469d1a6 to cf06e4a Compare May 27, 2025 12:56
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.

Extension changes syntax highlighting across all languages

2 participants