-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
The attribute brackets #1307
Comments
I asked once (#735), but didn't get an answer to why it was chosen. |
It's because it's so much easier for french people to type :D. |
Yes, @visionmedia is right that we definitely don't want two syntaxes for the same thing here. In some ways changing to the |
@ForbesLindesay I feel that depricating it now, and removing it 1 year down the line... it's a decent transition... Or have a fallback if all hell goes loose |
@ForbesLindesay so any light on this? |
@ForbesLindesay is this question open for discussion ? |
I think I'm going to leave it out for this release. It's a big change to make this close to the deadline. It is open for discussion for v2.0.0 and could be made in a backwards compatible (mostly) way by just allowing people to use either or (providing they match). |
-1 for |
I just don't think this change is worthwhile at the moment. Being more like CSS would be kind of nice, but I think it's fine as it is with the minor variation. |
I know this ticket is closed... but how about a setting/flag, where a user can override, what they should use Something like a config file, or just like we set This is very easy to change the default, and if there is a problem, you can change the flag very easily if you are on the old version. |
Hi Guys,
I have a question regarding the attributes round brackets...
Why was the decision to use
(href="#")
as oppose to[href="#"]
I would strongly recommend to use the square brackets as this is most commonly used in CSS selectors, jQuery and other languages use
[]
to reference the attribute list.Or at the very list, we could have the option to add that ourselves, or change preferences.
But I strongly believe it only makes sense to support both for the time being, depricate the
()
introduce the[]
and then when a new version is out (a year or so down the the line) remove the()
Any thoughts on this ?
The text was updated successfully, but these errors were encountered: