Closed davewalk closed 9 years ago
Attributes of a directive are really just examples of isolated scope. Is there an issue with using one time binding in the template via isolated scope? It doesn't fundamentally change anything. It's just more of the 'angular' way.
@davewalk that's a really good start!
My feedback,
closeIcon
attribute name, since it's more clear.default
implementation, so user just<notifications-bar class="notifications"></notifications-bar>
If she really want's to override close icon,
<notifications-bar class="notifications" closeIcon="my-custom-icon"></notifications-bar>
Otherwise, it looks great.
@alexbeletsky I changed iconClasses
to closeIcon
. Yes, the default is glyphicon glyphicon-remove
if the user does not define a closeIcon
attribute.
This is ready to go unless you see anything that needs to be changed. I didn't bump up the version # - didn't know if you wanted to do that.
Amazing job!
I'm merging that in :)
I'll pick up from here and try to intergrate the default close button as embedabble css style. So, it backward compatible and users don't need to do anything after upgrade.
After that I'll publish update.
This pull request will involve remove this plugin's dependency on the Glyphicons font library for displaying a close button in the notification bar (#18).
For now it just adds an
iconClasses
attribute to the directive that overrides the default "glyphicon glyphicon-remove close-click" classes if declared.@alexbeletsky @vikeen if this looks good to you I'll remove glyphicons in other places before merging:
iconClasses
attribute or at least import glyphicons somehow for the defaultfonts/
directory@import
in the main SASS fileexample/
directory so that the example app still works correctly with the defaultI think that covers everything.
Let me know! Thx!