-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
Prefix Ionic directives with 'ion-' #333
Comments
Not really necessary in my opinion - less typing and it's unlikely that you'll run into collisions - when will you ever have two side menus? |
Yep I am thinking the same thing. Ionic is gonna be the main framework used in an app, I didn't see any possible collisions so far with other components. |
Thanks for the input! I'm on the same page as well
|
Please reconsider this decision:
I see a lot of big UI frameworks failing to prefix and its really bothersome because you can't mix and match them. It's just too confusing/dangerous. |
@ewinslow sorry for the confusion, we already decided to prefix with |
Services are prefixed. Directives are not, according to this ticket |
They might not use a "main one" but any framework that provides similar
|
+1 for prefixing. Even Angular core directives have the |
I'm down for it. One benefit is it makes it clear which directives do something. Maybe |
👍 for On Sat, Feb 8, 2014 at 2:43 PM, Max Lynch notifications@github.com wrote:
|
It would also be cool to link people to a script which they could run to On Sat, Feb 8, 2014 at 2:44 PM, Andy Joslin andytjoslin@gmail.com wrote:
|
You guys are great for reconsidering this. Maybe it would make sense to reopen this issue? |
I think we should do this and vote for |
👍 Great decision. I vote for ion- |
I vote for ion as well. It's kind of fun, like little ions all over the page! |
Oh and @ewinslow, I like to think we are somewhat reasonable people ;) |
:). Now if I can get you to prefix the classes too, that would really seal the deal! |
@ewinslow I said somewhat reasonable, that's just ludicrous! ;) |
Guess I better go make my case then... |
Directive prefixing is scheduled for the 0.9.25 release. |
Closed 2c39a21 |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
We are debating whether to add prefixes to Ionic directives. So, instead of doing
<side-menus>
it would be<ionic-side-menus>
or<ion-side-menus>
. Nav router would be<div ionic-nav-router>
or<div ion-nav-router>
instead of<div nav-router>
.The arguments for making the change is it makes it more clear which directives are ionic-powered, and which ones aren't. Also it reduces the possibility of clashes with other directives from other libraries.
The arguments against are that it adds extra clutter, makes the code less pretty IMO, and might not be necessary if Ionic has most of the features we need.
We'd love to hear thoughts and opinions on this change.
The text was updated successfully, but these errors were encountered: