Skip to content
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

Token type guidelines #2083

Open
RunDevelopment opened this issue Sep 30, 2019 · 0 comments
Open

Token type guidelines #2083

RunDevelopment opened this issue Sep 30, 2019 · 0 comments

Comments

@RunDevelopment
Copy link
Member

RunDevelopment commented Sep 30, 2019

Motivation
While the type of a token is generally constraint by the ones Prism's themes support, the authors of language definitions have to choose within this set of supported token which might not perfectly match their language.

The goal of this issue is to establish guidelines to keep the token types across languages consistent and to publish these guidelines on the Prism website.

#2073 started it all.

Description
So far, there's only one guideline by @mAAdhaTTah.

  1. Don't make any token "punctuation" if it fits into another token type. In other words, "punctuation" is a token of last resort.

  2. "true" and "false" or any two literal pairs which express the same concept are "boolean" tokens.


@Golmote @mAAdhaTTah I would like to collect a few guidelines and make them their own section here. This section will also contain information about what token types are available.

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

No branches or pull requests

1 participant