ng-japan
2015
@Chirayuk

Angular 1.4


The best Angular today!



Community

Community Engagements

- 100K+ unique GitHub visitors / 2 week - ~ 1600 new issues and PRs created - ~ 200 new contributors

Commits

What's New in 1.4?

  • Weekly release candidates
  • 35+ new features
  • 140+ bugs fixed
  • Performance improvements

What's New in 1.4?

  • New Router
  • Pluralization and Gender support
  • ng-animate update
  • ng-messages update
  • ng-cookies update

New Router

Watch
Brian's talk @ 15:10

Pluralization and Gender

  • Based on ICU MessageFormat
  • Use in interpolation expressions
  • Use in attributes

Pluralization

{{numMessages, plural,
      =0 { You have no new messages }
      =1 { You have one new message }
   other { You have # new messages }
}}

Gender

{{friendGender, select,
       male { Invite him }
     female { Invite her }
      other { Invite them }
}}

ng-messages updates

- New ngMessages with multiple `includes` - More dynamic messages

ng-cookies updates

- Ability to set path and domain - Cleans up cookie update process - Closes one of the oldest and most commented open issues :-)

What's new (more)

  • CommonJS-friendly builds
  • injector - print caller name in "unknown provider" errors
  • ng-jq - make it possible to force jqLite or a specific jQuery version
  • ngOptions - add support for disabling an option
  • limitTo - add a beginning index argument
  • ngModel - add $setDirty method
  • routeProvider - allow case-insensitive route matching
  • ngAria improvements
  • $http improvements

Better Performance

  • ~30% faster digest times (vs Angular 1.3)
  • 2-4% memory footprint improvement
    • Less GC pressure
  • Performance improvements varies
    depending on browser/application

Everyone should upgrade!

  • Very few breaking changes
  • Same browsers supported as in 1.3

Future

Angular 1.5

- Work will start after 1.4.0 is out - Planning will happen in public - Community involvement is the key - Comment / vote on issues you want to see fixed - Send pull requests

Angular 2


Watch
Igor's talk @ 17:10

Shorter release cycles

You

can help!

❶  Add a Feature

  • Contact us
  • Minimal set of changes per PR
  • Unit tests
  • Follow conventions

❷  Work on Issues

  • Write a Plunker or a failing test
  • Broken at master?

❸  Help closing issues and PRs

When they are no longer valid/relevant

Thanks!