| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
The cancel function accepts a Promise, but the timeout function
fails to specify returning a Promise.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Making testacular a dependency to avoid having to install it globally.
(Causes npm issues on some machines)
|
|
Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.
Closes #1401
|
|
|
|
Fix table formatting so headings are bold, rows are separated by lines, and rows have :hover style
|
|
fixed example app, `simpleAppModule` should have been `myAppModule`.
|
|
|
|
Prefixed attributes like data-ng-model and x-ng-model were not being
found by the Selector. It was only looking at ng: and ng- prefixed
attributes.
Added a few tests as well to ensure the aforementioned prefixed
attributes are being matched properly.
Closes #1020
|
|
|
|
previously examples like $http where broken because we would strip part of the
filename (http-hello.html -> http)
we really want to strip only the id suffix that we append to disambiguate
common filenames (like index.html) which appear in many examples.
|
|
Add option to edit source in Angular Docs in Plunkr in addition to JsFiddle
|
|
Closes #1493
|
|
if className is undefined or empty string, don't bother looking for directives in there
|
|
if a node doesn't have children then don't try to compile these non-existent children
|
|
|
|
|
|
This fixes the issue that caused two attr interpolation observers
to be registered for the same attribute as a result of isolate
scope definition with attr (@) property for this attribute.
Duplicate observers would then fight with each other updating the
model.
The issue occured only when this directive was used in a repeater
because that's when we clone the template node which caused the
two observers to point to two different sets of $attr instances.
Closes #1166, #836
|
|
IEEE 754 floating point sometimes results in values that are very small,
rather than zero. One example is 1.0 + 1.07 - 2.07, which returns
4.440892098500626e-16 instead of 0.
This change tweaks the number formatting logic so that an exponential
value with a negative exponent that is larger than the precision+1
returns 0 instead. For example: with precision 2, anything with an
exponent of -4, -5 or more would become 0. 9e-3 = 0.009 = 0.01, but 9e-4
= 0.0009 = 0.001 = 0.00. This detail is unlikely to matter since this
quirk is usually only triggered with values very close to zero.
Closes #1469
|
|
Describes several common pitfalls new users of Angular fall into that
I've observed in #angularjs.
|
|
|
|
|
|
|
|
|
|
|
|
it's bundled with Testacular, so we don't need it here
|
|
Testacular FTW!
|
|
JsTD references have been replaced with Testacular stuff.
snapshots are PITA to maintain so I'm dropping them, everyone loves the Git
version anyway.
|
|
|
|
Using the client VM and forcing 32bit mode gives us huge perf boost.
before:
reali 0m8.173s
user 0m39.984s
sys 0m1.408s
after:
real 0m3.000s
user 0m12.687s
sys 0m0.852s
|
|
this speeds up the build by paralelizing closure compilation (the slowest
piece of the build process)
before:
real 0m14.372s
user 0m31.649s
sys 0m1.006s
after:
real 0m8.191s
user 0m40.473s
sys 0m1.378s
|
|
|
|
|
|
exec unlike system replaces the current process. this way when we kill
the webserver process we don't get scary looking 'rake aborted' error
|
|
|
|
|
|
|
|
This was really corner case:
Watcher needs to return changed value, to notify that model might have changed and one more $digest cycle needs to be performed.
The watcher, that takes care of reference binding into an isolate scope ("="), did not return changed value, if the change was from the isolate scope to the parent.
If any other watcher returned change, it worked fine, as this change caused re-digest.
Closes #1272
|
|
|
|
|