Say we have html structure like this:
<div id="parent"> <h1></h1> <p></p> <p></p> </div>
What would this selector have selected?
#parent{ p:first-child{} }
Say we have html structure like this:
<div id="parent"> <h1></h1> <p></p> <p></p> </div>
What would this selector have selected?
#parent{ p:first-child{} }
Links: Github Repo / Live Demo
Angular directive, with recursive support for multiple layers of checkboxes.
For me the revelation came when I realised that they all work the same way: by running something once, storing the value they get, and then cough up that same stored value when referenced through Dependency Injection.
Could you tell the difference between these four?
$scope.$watch('foo', fn)
$scope.$watch(function() {return $scope.foo}, fn)
$scope.$watch(obj.prop, fn)
$scope.$watch(function() {return obj.prop}, fn)
$(document)
. Other firing of events would depend on the $emit
of scope events.click-elsewhere="show=false"
, and click-elsewhere="fn()"
, thanks to $parse
.I was thinking about it: what purpose should a blog serve?
Have this list firmly registered somewhere in the back of your head before embarking on Angular! I can’t tell you how much confusion and pain not realising its existence has caused me. These are the keywords I used to find all the directives that create scope, thanks to @sp00m’s prompt.
Providing that Angular’s documentation is consistent in the way they describe directives, which it seems to be, below is the full list of results, in order of priority level of execution:
terminal
$ sudo ln -s "/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" /bin/subl
vimrc
map <silent><leader>os : exe 'silent !subl .'<CR>