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

Consider a different way to distinguish class names from named style parameters #33

Open
darioteixeira opened this issue Mar 26, 2015 · 0 comments

Comments

@darioteixeira
Copy link
Owner

@darioteixeira darioteixeira commented Mar 26, 2015

Presently, two different specifications fall under the style parameters umbrella: attaching an arbitrary classname to an element, and configuration using element-specific named parameters of the form key=value. The presence of the equal sign is used to distinguish one from the other.
#29 is just one example of why it would be useful if a different mechanism were used to distinguish between the two uses. Two alternatives come to mind:

  1. Break apart style parameters into two distinct parameter categories, each with different markers. Unfortunately, we already make use of square, round, angle, and curly brackets, and users will frown upon the adoption of exotic Unicode characters. Digraphs are a way around this conundrum, but suffer from ugliness and should only be adopted as a last resort. Another idea is to use double quotes as markers, though they're not much prettier than digraphs.

  2. Keep the two uses of style parameters under the same umbrella, but use something other the equal sign to distinguish between them. One possibility is to require classnames to be quoted or double-quoted.

@darioteixeira darioteixeira mentioned this issue Aug 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.