| Age | Commit message (Collapse) | Author |
|
|
|
|
|
we commonly assign stuff in if statments like this:
if (variable = someFn()) {
//do something with variable
}
This results in lint and IDE warnings (did you mean ==?).
It is better to be explicit about our intention and wrap the assignement
into parens:
if ((variable = someFn())) {
//do something with variable
}
Doing so suppresses warnings + is easier to understand the intention.
I verified that the closure compiler strips the extra parens, so there
is no byte overhead for this safety practice.
We should use this style going forward...
|
|
|
|
|
|
The support for the 'z' formatting flag was removed becase the timezone
info can't be retrieved from the browser apis (except for en-US locale
on some but not all browsers). For this reason we don't want to support
this flag at all.
Related to this, since the 'long' and 'longtime' datetime formats require
the 'z' flag in the formatting string, we are removing support for this
format as well.
|
|
- add i18n/closure directory with closure i18n files and
update-closure.sh script to update them
- generate.sh script runs node.js scripts that extract localization
rules from the closure library, transform them to a more suitable
format and dumps them into i18n/locale directory as angular's $locale
services
- update Rakefile to copy i18n files to build/ and pkg/ dirs
- copy i18n stuff during rake build
- e2e tests for several locales
|
|
- filter.number, filter.currency and filter.date are injected with
$locale service so that we can just swap the service to localize these
- date filter was beefed up in order to support literal strings found in
localization rules
|
|
|
|
Closes #508
|
|
|
|
Much faster $destroy operations for large ng:repeat sets.
|
|
|
|
|
|
|
|
|
|
|
|
This was causing to show up the "$browser" twice in the menu.
|
|
Closes #506
|
|
|
|
windgets
These widgets are useless and only trigger extra $updateViews.
The only reason we had them was to support ng:change on these widgets,
but since there are no bindings present in these cases it doesn't make
sense to support ng:change here. It's likely just a leftover from
getangular.com
Breaking change: ng:change for input[button], input[submit], input[reset], input[image]
and button widgets is not supported any more
|
|
- add e2e tests
- refactor the example by removing clear button and simplifying the code
|
|
since we don't know if the error was due to a client error (4xx) or
server error (5xx), we leave the status code as undefined.
|
|
|
|
- must use binary reading when using read function in q-fs module
otherwise some unicode character may be garbled.
Closes #497
|
|
$xhr.error's first argument (request) has no callback property anymore,
it's called success now...
This breaking change was introduced by b5594a773a6f07dcba914aa385f92d3305285b24
|
|
- the end index for slice, if not specified, is default to the
end of the array it operates on.
|
|
- Speed improvements (about 4x on flush phase)
- Memory improvements (uses no function closures)
- Break $eval into $apply, $dispatch, $flush
- Introduced $watch and $observe
Breaks angular.equals() use === instead of ==
Breaks angular.scope() does not take parent as first argument
Breaks scope.$watch() takes scope as first argument
Breaks scope.$set(), scope.$get are removed
Breaks scope.$config is removed
Breaks $route.onChange callback has not "this" bounded
|
|
Minor documentation fixes. Should not be any code changes.
One test changed due to dependency on text in documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Users often don't see Tutorial and go straight to crappy Dev Guide,
changing the order should help find them right content in the right
order.
|
|
|
|
|
|
|
|
|
|
The arrow is a hint that user won't navigate to a new page, but instead
the instructions will be displayed inline.
|
|
Closes #408
|
|
|
|
|
|
|
|
|
|
The previous implementation didn't handle situation when in css
something was hidden with a cascaded display:none rule and then we
wanted to show it.
Unfortunatelly our test doesn't test this scenario because it's too
complicated. :-/
|
|
jqLite doesn't support class selectors, can find only by tag name...
|
|
both numbers and currency need to be formatted using a generic pattern
which can be replaced for a different pattern when angular is working in
a non en-US locale
for now only en-US locale is supported, but that will change in the
future
|