angular-cookies - npm Package Versions

1.3.11 spiffy-manatee (2015-01-26)

Bug Fixes

• $location: don't rewrite when link is shift-clicked (939ca37c, #9904, #9906)
• htmlAnchorDirective:
  • remove "element !== target element" check (779e3f6b, #10866)
  • don't add event listener if replaced, ignore event if target is different element (837a0775, #4262, #10849)

<a name="1.4.0-beta.1"></a>

1.4.0-beta.2 holographic-rooster (2015-01-26)

Bug Fixes

• $location: don't rewrite when link is shift-clicked (8b33de6f, #9904, #9906)
• $templateRequest: cache downloaded templates as strings (b3a9bd3a, #10630, #10646)
• filterFilter: throw error if input is not an array (cea8e751, #9992, #10352)
• htmlAnchorDirective:
  • remove "element !== target element" check (2958cd30, #10866)
  • don't add event listener if replaced, ignore event if target is different element (b146af11, #4262, #10849)
• ngPluralize: fix wrong text content when count is null/undefined (3228d3b4, #10836, #10841)

Breaking Changes

• filterFilter: due to cea8e751, Previously, the filter was not applied if used with a non array. Now, it throws an error. This can be worked around by converting an object to an array, using a filter such as https://github.com/petebacondarwin/angular-toArrayFilter

Closes #9992 Closes #10352

<a name="1.3.11"></a>

1.4.0-beta.1 trepidatious-salamander (2015-01-20)

Bug Fixes

• $animate: ensure no transitions are applied when an empty inline style object is provided (0db5b21b, #10613, #10770)
• $compile: support class directives on SVG elements (23c8a90d, #10736, #10756)
• form: clean up success state of controls when they are removed (2408f2de, #10509)
• ngController: allow bound constructor fns as controllers (d17fbc38, #10784, #10790)
• ngRepeat: do not sort object keys alphabetically (c260e738, #6210, #10538)

Features

• $http: provide a config object as an argument to header functions (d435464c, #7235, #10622)

Breaking Changes

• ngRepeat: due to c260e738,

Previously, the order of items when using ngRepeat to iterate over object properties was guaranteed to be consistent by sorting the keys into alphabetic order.

Now, the order of the items is browser dependent based on the order returned from iterating over the object using the for key in obj syntax.

It seems that browsers generally follow the strategy of providing keys in the order in which they were defined, although there are exceptions when keys are deleted and reinstated. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/delete#Cross-browser_issues

The best approach is to convert Objects into Arrays by a filter such as https://github.com/petebacondarwin/angular-toArrayFilter or some other mechanism, and then sort them manually in the order you need.

Closes #6210 Closes #10538

<a name="1.3.10"></a>

1.3.10 heliotropic-sundial (2015-01-20)

Bug Fixes

• $animate: ensure no transitions are applied when an empty inline style object is provided (9b8df52a, #10613, #10770)
• $compile: support class directives on SVG elements (7a9e3360, #10736, #10756)
• form: clean up success state of controls when they are removed (cdc7280d, #10509)
• ngController: allow bound constructor fns as controllers (d015c8a8, #10784, #10790)

<a name="1.4.0-beta.0"></a>

1.3.9 multidimensional-awareness (2015-01-13)

Bug Fixes

• $parse: allow use of locals in assignments (86900814)
• filterFilter: use isArray() to determine array type (d4b60ada, #10621)

Features

• ngMock/$exceptionHandler: log errors when rethrowing (2b97854b, #10540, #10564)

Performance Improvements

• ngStyleDirective: use $watchCollection (4c8d8ad5, #10535)

<a name="1.3.8"></a>

1.4.0-beta.0 photonic-umbrakinesis (2015-01-13)

Bug Fixes

• $location: support right button click on anchors in firefox (aa798f12, #7984)
• $templateRequest: propagate HTTP status on failed requests (e24f22bd, #10514, #10628)
• dateFilter: ignore invalid dates (1334b8c8, #10640)
• filterFilter: use isArray() to determine array type (a01ce6b8, #10621)
• ngChecked: ensure that ngChecked doesn't interfere with ngModel (e079111b, #10662, #10664)
• ngClass: handle multi-class definitions as an element of an array (e1132f53, #8578, #10651)
• ngModelOptions: allow sharing options between multiple inputs (9c9c6b3f, #10667)
• ngOptions:
  • support one-time binding on the option values (ba90261b, #10687, #10694)
  • prevent infinite digest if track by expression is stable (fc21db8a, #9464)
  • update model if selected option is removed (933591d6, #7736)
  • ensure that the correct option is selected when options are loaded async (7fda214c, #8019, #9714, #10639)
• ngPluralize: generate a warning when using a not defined rule (c66b4b6a)

Features

• $filter: display Infinity symbol when number is Infinity (51d67742, #10421)
• $timeout: allow fn to be an optional parameter (5a603023, #9176)
• limitTo: ignore limit when invalid (a3c3bf33, #10510)
• ngMock/$exceptionHandler: log errors when rethrowing (deb3cb4d, #10540, #10564)

Performance Improvements

• ngStyleDirective: use $watchCollection (8928d023, #10535)

Breaking Changes

• limitTo: due to a3c3bf33, limitTo changed behavior when limit value is invalid. Instead of returning empty object/array it returns unchanged input.

• ngOptions: due to 7fda214c,

When using ngOptions: the directive applies a surrogate key as the value of the <option> element. This commit changes the actual string used as the surrogate key. We now store a string that is computed by calling hashKey on the item in the options collection; previously it was the index or key of the item in the collection.

(This is in keeping with the way that the unknown option value is represented in the select directive.)

Before you might have seen:

<select ng-model="x" ng-option="i in items">
  <option value="1">a</option>
  <option value="2">b</option>
  <option value="3">c</option>
  <option value="4">d</option>
</select>

Now it will be something like:

<select ng-model="x" ng-option="i in items">
  <option value="string:a">a</option>
  <option value="string:b">b</option>
  <option value="string:c">c</option>
  <option value="string:d">d</option>
</select>

If your application code relied on this value, which it shouldn't, then you will need to modify your application to accommodate this. You may find that you can use the track by feature of ngOptions as this provides the ability to specify the key that is stored.

• ngOptions: due to 7fda214c,

When iterating over an object's properties using the (key, value) in obj syntax the order of the elements used to be sorted alphabetically. This was an artificial attempt to create a deterministic ordering since browsers don't guarantee the order. But in practice this is not what people want and so this change iterates over properties in the order they are returned by Object.keys(obj), which is almost always the order in which the properties were defined.

• ngOptions: due to 7fda214c,

setting the ngOptions attribute expression after the element is compiled, will no longer trigger the ngOptions behavior. This worked previously because the ngOptions logic was part of the select directive, while it is now implemented in the ngOptions directive itself.

• select: due to 7fda214c,

the select directive will now use strict comparison of the ngModel scope value against option values to determine which option is selected. This means Number scope values will not be matched against numeric option strings. In AngularJS 1.3.x, setting scope.x = 200 would select the option with the value 200 in the following select:

<select ng-model="x">
  <option value="100">100</option>
  <option value="200">200</option>
</select>

In AngularJS 1.4.x, the 'unknown option' will be selected. To remedy this, you can simply initialize the model as a string: scope.x = '200', or if you want to keep the model as a Number, you can do the conversion via $formatters and $parsers on ngModel:

ngModelCtrl.$parsers.push(function(value) {
  return parseInt(value, 10); // Convert option value to number
});

ngModelCtrl.$formatters.push(function(value) {
  return value.toString(); // Convert scope value to string
});

<a name="1.3.9"></a>

1.3.8 prophetic-narwhal (2014-12-19)

Bug Fixes

• filterFilter:
  • make $ match properties on deeper levels as well (bd28c74c, #10401)
  • let expression object {$: '...'} also match primitive items (fb2c5858, #10428)
• ngAria: trigger digest on ng-click via keypress, pass $event to expression (924e68c7, #10442, #10443, #10447)
• orderBy: compare timestamps when sorting date objects (661f6d9e, #10512, #10516)

Performance Improvements

• limitTo: replace for loop with slice (cd77c089)

<a name="1.3.7"></a>

1.2.28 finnish-disembarkation (2014-12-15)

Bug Fixes

• $route: fix redirection with optional/eager params (1b9e408d, #9742, #10202)
• linky: encode double quotes when serializing email addresses (929dd15b, #8945, #8964, #5946, #10090, #9256)

<a name="1.3.6"></a>

1.3.7 leaky-obstruction (2014-12-15)

Bug Fixes

• $compile: use createMap() for $$observe listeners when initialized from attr interpolation (8e28bb4c)
• $http:
  • only parse as JSON when opening/closing brackets match (b9bdbe61, #10349, #10357)
  • don't convert FormData objects to JSON (40258838, #10373)
• $parse: a chain of field accessors should use a single getterFn (c90ad968)
• ngRepeat: allow extra whitespaces in (key,value) part of micro-syntax (ef640cbc, #6827, #6833)
• orderBy: do not try to call valueOf/toString on null (a097aa95, #10385, #10386)

Features

• $compile: add support for ng-attr with camelCased attributes (d8e37078, #9845, #10194)
• $http: pass response status code to data transform functions (1b740974, #10324, #6734, #10440)
• $rootScope: allow passing locals argument to $evalAsync (9b96cea4, #10390)

Performance Improvements

• $compile: only re-$interpolate attribute values at link time if changed since compile (9ae0c01c)

Breaking Changes

• orderBy: due to a097aa95,

Previously, if either value being compared in the orderBy comparator was null or undefined, the order would, incorrectly, not change. Now, this order behaves more like Array.prototype.sort, which by default pushes null behind objects, due to n occurring after [ (the first characters of their stringified forms) in ASCII / Unicode. If toString is customized, or does not exist, the behavior is undefined.

<a name="1.2.28"></a>

1.3.6 robofunky-danceblaster (2014-12-08)

Bug Fixes

• $browser: prevent infinite digests when clearing the hash of a url (10ac5948, #9629, #9635, #10228, #10308)
• $http: preserve config object when resolving from cache (facfec98, #9004, #9030)
• $location:
  • allow hash fragments with hashPrefix in hash-bang location urls (2dc34a96, #9629, #9635, #10228, #10308)
  • strip off empty hash segments when comparing (e93710fe, #9635)
• $parse:
  • fix operators associativity (ed1243ff)
  • follow JavaScript context for unbound functions (429938da)
• filterFilter:
  • don't match primitive sub-expressions against any prop (a75537d4)
  • ignore function properties and account for inherited properties (5ced914c, #9984)
  • correctly handle deep expression objects (f7cf8460, #7323, #9698, #9757)
• inputs: ignoring input events in IE caused by placeholder changes or focus/blur on inputs with placeholders (55d9db56, #9265)
• linky: make urls starting with www. links, like markdown (915a891a, #10290)
• ngAnimate: do not use jQuery class API (40a537c2, #10024, #10329)
• ngMock: allow numeric timeouts in $httpBackend mock (acb066e8, #4891)
• ngModel:
  • always use the most recent viewValue for validation (2d6a0a1d, #10126, #10299)
  • fixing many keys incorrectly marking inputs as dirty (d21dff21)
• ngSanitize: exclude smart quotes at the end of the link (7c6be43e, #7307)
• numberFilter: numbers rounding to zero shouldn't be negative (96c61fe7, #10278)
• orderBy:
  • make object-to-primitive behavior work for objects with null prototype (3aa57528)
  • maintain order in array of objects when predicate is not provided (8bfeddb5, #9566, #9747, #10311)

Features

• $$jqLite: export jqLite as a private service (f2e7f875)
• $injector: print caller name in "unknown provider" errors (when available) (013b522c, #8135, #9721)
• jsonFilter: add optional arg to define custom indentation (1191edba, #9771)
• ngAria: bind keypress on ng-click w/ option (5481e2cf, #10288)

Breaking Changes

• $location: due to 2dc34a96,

We no longer throw an ihshprfx error if the URL after the base path contains only a hash fragment. Previously, if the base URL was http://abc.com/base/ and the hashPrefix is ! then trying to parse http://abc.com/base/#some-fragment would have thrown an error. Now we simply assume it is a normal fragment and that the path is empty, resulting $location.absUrl() === "http://abc.com/base/#!/#some-fragment".

This should not break any applications, but you can no longer rely on receiving the ihshprfx error for paths that have the syntax above. It is actually more similar to what currently happens for invalid extra paths anyway: If the base URL and hashPrfix are set up as above, then http://abc.com/base/other/path does not throw an error but just ignores the extra path: http://abc.com/base.

• filterFilter: due to a75537d4,

  Named properties in the expression object will only match against properties on the same level. Previously, named string properties would match against properties on the same level or deeper.

  Before:

  arr = filterFilter([{level1: {level2: 'test'}}], {level1: 'test'});   // arr.length -> 1
  

  After:

  arr = filterFilter([{level1: {level2: 'test'}}], {level1: 'test'});   // arr.length -> 0
  

  In order to match deeper nested properties, you have to either match the depth level of the property or use the special $ key (which still matches properties on the same level or deeper). E.g.:

  // Both examples below have `arr.length === 1`
  arr = filterFilter([{level1: {level2: 'test'}}], {level1: {level2: 'test'}});
  arr = filterFilter([{level1: {level2: 'test'}}], {$: 'test'});
  

<a name="1.3.5"></a>