Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

angular-scenario

Package Overview
Dependencies
Maintainers
3
Versions
99
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

angular-scenario - npm Package Versions

1
10

1.4.0-rc.1

Diff

Changelog

Source

v1.4.0-rc.1 sartorial-chronography (2015-04-24)

Bug Fixes

  • $animate:
    • ensure that from styles are applied for class-based animations (8f819d2c)
    • make sure the JS animation lookup is an object lookup (103a39ca, #11619)
  • $animateCss: ensure that rAF waiting loop doesn't ignore pending items during a flush (90e424b2)
  • $http: stop coercing falsy HTTP request bodies to null / empty body (e04a887c, #11552, #11593)
  • ngAnimate:
    • close parent animations only when there are classes to resolve (1459be17)
    • ensure ngClass-based classes are always resolved for CSS-enabled animations (89f081e4)
    • do not abort animation if only ng-anchor-in is used (3333a5c3)
    • ensure that a filtered-out leave animation always runs its DOM operation (6dd64ab5, #11555)
    • ensure that animations work when the app is bootstrapped on the document node (bee14ed1, #11574)
    • ensure SVG classes are properly removed (fa0bbded)
  • ngAria: change accessibility keypress event to use event.which if it is provided (249f9b81, #11340)
  • ngMessageFormat:
  • select: allow empty option to be added dynamically by ng-repeat (abf59c28, #11470, #11512)

Features

  • $animate: provide support for animations on elements outside of $rootElement (e41faaa2)

<a name="v1.4.0-rc.0"></a>

angularcore
published 1.4.0-rc.0 •

Changelog

Source

v1.4.0-rc.0 smooth-unwinding (2015-04-10)

Bug Fixes

Features

Performance Improvements

Breaking Changes

  • $animate: due to c8700f04, JavaScript and CSS animations can no longer be run in parallel. With earlier versions of ngAnimate, both CSS and JS animations would be run together when multiple animations were detected. This feature has now been removed, however, the same effect, with even more possibilities, can be achieved by injecting $animateCss into a JavaScript-defined animation and creating custom CSS-based animations from there. Read the ngAnimate docs for more info.

  • $animate: due to c8700f04, The function params for $animate.enabled() when an element is used are now flipped. This fix allows the function to act as a getter when a single element param is provided.

// < 1.4
$animate.enabled(false, element);

// 1.4+
$animate.enabled(element, false);
  • $animate: due to c8700f04, In addition to disabling the children of the element, $animate.enabled(element, false) will now also disable animations on the element itself.

  • $animate: due to c8700f04, Animation-related callbacks are now fired on $animate.on instead of directly being on the element.

// < 1.4
element.on('$animate:before', function(e, data) {
  if (data.event === 'enter') { ... }
});
element.off('$animate:before', fn);

// 1.4+
$animate.on(element, 'enter', function(data) {
  //...
});
$animate.off(element, 'enter', fn);
  • $animate: due to c8700f04, There is no need to call $scope.$apply or $scope.$digest inside of an animation promise callback anymore since the promise is resolved within a digest automatically (but a digest is not run unless the promise is chained).
// < 1.4
$animate.enter(element).then(function() {
  $scope.$apply(function() {
    $scope.explode = true;
  });
});

// 1.4+
$animate.enter(element).then(function() {
  $scope.explode = true;
});
  • $animate: due to c8700f04, When an enter, leave or move animation is triggered then it will always end any pending or active parent class based animations (animations triggered via ngClass) in order to ensure that any CSS styles are resolved in time.

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

angularcore
published 1.3.15 •

Changelog

Source

1.3.15 locality-filtration (2015-03-17)

Bug Fixes

Features

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

angularcore
published 1.4.0-beta.6 •

Changelog

Source

1.4.0-beta.6 cookie-liberation (2015-03-17)

Bug Fixes

  • $animate: call applyStyles from options on leave (4374f892, #10068)
  • $browser: don't crash if history.state access causes error in IE (3b8163b7, #10367, #10369)
  • $sanitize: disallow unsafe svg animation tags (67688d5c, #11290)
  • Angular: properly compare RegExp with other objects for equality (f22e1fc9, #11204, #11205)
  • date filter: display localized era for G format codes (2b4dfa9e, #10503, #11266)
  • filterFilter:
  • form: allow dynamic form names which initially evaluate to blank (410f7c68)
  • jqLite: attr should ignore comment, text and attribute nodes (bb5bf7f8)
  • ng/$locale: add ERA info in generic locale (4acb0af2)
  • ngJq: don't rely on existence of jqlite (342e5f3c, #11044)
  • ngMessages: ensure that multi-level transclusion works with ngMessagesInclude (d7ec5f39, #11196)
  • ngOptions: fix model<->option interaction when using track by (6a03ca27, #10869, #10893)
  • rootScope: prevent memory leak when destroying scopes (fb7db4a0, #11173, #11169)

Features

Breaking Changes

$cookies no longer exposes properties that represent the current browser cookie values. Now you must explicitly the methods described above to access the cookie values. This also means that you can no longer watch the $cookies properties for changes to the browser's cookies.

This feature is generally only needed if a 3rd party library was programmatically changing the cookies at runtime. If you rely on this then you must either write code that can react to the 3rd party library making the changes to cookies or implement your own polling mechanism.

<a name="1.3.15"></a>

angularcore
published 1.4.0-beta.5 •

Changelog

Source

1.4.0-beta.5 karmic-stabilization (2015-02-24)

Bug Fixes

Features

  • CommonJS: - angular modules are now packaged for npm with helpful exports

  • limitTo: extend the filter to take a beginning index argument (aaae3cc4, #5355, #10899)

  • ngMessages: provide support for dynamic message resolution (c9a4421f, #10036, #9338)

  • ngOptions: add support for disabling an option (da9eac86, #638, #11017)

Performance Improvements

  • $compile:
    • replace forEach(controller) with plain loops (5b522867, #11084)
    • avoid .data when fetching required controllers (fa0aa839)
  • ngOptions: only watch labels if a display expression is specified (51faaffd)

Breaking Changes

The ngMessagesInclude attribute is now its own directive and that must be placed as a child element within the element with the ngMessages directive. (Keep in mind that the former behavior of the ngMessageInclude attribute was that all included ngMessage template code was placed at the bottom of the element containing the ngMessages directive; therefore to make this behave in the same way, place the element containing the ngMessagesInclude directive at the end of the container containing the ngMessages directive).

<!-- AngularJS 1.3.x -->
<div ng-messages="model.$error" ng-messages-include="remote.html">
  <div ng-message="required">Your message is required</div>
</div>

<!-- AngularJS 1.4.x -->
<div ng-messages="model.$error">
  <div ng-message="required">Your message is required</div>
  <div ng-messages-include="remote.html"></div>
</div>

it is no longer possible to use interpolation inside the ngMessages attribute expression. This technique is generally not recommended, and can easily break when a directive implementation changes. In cases where a simple expression is not possible, you can delegate accessing the object to a function:

<div ng-messages="ctrl.form['field_{{$index}}'].$error">...</div>

would become

<div ng-messages="ctrl.getMessages($index)">...</div>

where ctrl.getMessages()

ctrl.getMessages = function($index) {
  return ctrl.form['field_' + $index].$error;
}

transformRequest functions can no longer modify request headers.

Before this commit transformRequest could modify request headers, ex.:

function requestTransform(data, headers) {
    headers = angular.extend(headers(), {
      'X-MY_HEADER': 'abcd'
    });
  }
  return angular.toJson(data);
}

This behavior was unintended and undocumented, so the change should affect very few applications. If one needs to dynamically add / remove headers it should be done in a header function, for example:

$http.get(url, {
  headers: {
    'X-MY_HEADER': function(config) {
      return 'abcd'; //you've got access to a request config object to specify header value dynamically
    }
  }
})

<a name="1.3.14"></a>

angularcore
published 1.3.14 •

Changelog

Source

1.3.14 instantaneous-browserification (2015-02-24)

Features

  • CommonJS: - angular modules are now packaged for npm with helpful exports

Bug Fixes

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

angularcore
published 1.4.0-beta.4 •

Changelog

Source

1.4.0-beta.4 overlyexplosive-poprocks (2015-02-09)

Bug Fixes

Features

  • ng-jq: adds the ability to force jqLite or a specific jQuery version (09ee82d8)

<a name="1.3.13"></a>

angularcore
published 1.3.13 •

Changelog

Source

1.3.13 meticulous-riffleshuffle (2015-02-09)

Bug Fixes

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

angularcore
published 1.3.12 •

Changelog

Source

1.3.12 outlandish-knitting (2015-02-02)

Bug Fixes

  • $controller: throw better error when controller expression is bad (632b2ddd, #10875, #10910)
  • $parse: remove references to last arguments to a fn call (7caad220, #10894)
  • ngRoute: don't duplicate optional params into query (f41ca4a5, #10689)
  • ngScenario: Allow ngScenario to handle lazy-loaded and manually bootstrapped applications (0bcd0872, #10723)
  • validators: maxlength should use viewValue for $isEmpty (abd8e2a9, #10898)

Features

  • ngMocks: cleanup $inject annotations after each test (6ec59460)

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

angularcore
published 1.4.0-beta.3 •

Changelog

Source

1.4.0-beta.3 substance-mimicry (2015-02-02)

Bug Fixes

  • $compile:
    • do not initialize optional '&' binding if attribute not specified (6a38dbfd, #6404, #9216)
    • respect return value from controller constructor (62d514b0)
  • $controller: throw better error when controller expression is bad (dda65e99, #10875, #10910)
  • $parse:
  • a: don't reload if there is only a name attribute (d729fcf0, #6273, #10880)
  • angular.copy: support copying TypedArrays (aa0f6449, #10745)
  • filter: format timezone correctly in the case that UTC timezone is used (8c469191, #9359)
  • ngRoute: don't duplicate optional params into query (27bf2ce4, #10689)
  • ngScenario: allow ngScenario to handle lazy-loaded and manually bootstrapped applications (c69caa7b, #10723)
  • validators: maxlength should use viewValue for $isEmpty (bfcf9946, #10898)

Features

  • $compile: allow using bindToController as object, support both new/isolate scopes (35498d70, #10420, #10467)
  • filter: support conversion to timezone other than UTC (c6d8512a, #10858)
  • ngMocks: cleanup $inject annotations after each test (0baa17a3)

Performance Improvements

  • $scope: Add a property $$watchersCount to scope (c1500ea7)
  • $parse new and more performant parser (0d42426)

Breaking Changes

  • $compile: due to 6a38dbfd, Previously, '&' expressions would always set up a function in the isolate scope. Now, if the binding is marked as optional and the attribute is not specified, no function will be added to the isolate scope.

<a name="1.3.12"></a>

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc