fixes #3924 BREAKING CHANGE The `lifecycle` configuration for directive has been dropped. Before // Dart @Component({lifecycle: const [LifecycleEvent.OnChanges], ...}) class MyComponent implements OnChanges { void onChanges() {...} } // Typescript @Component({lifecycle: [LifecycleEvent.OnChanges], ...}) class MyComponent implements OnChanges { onChanges(): void {...} } // ES5 var MyComponent = ng. Component({lifecycle: [LifecycleEvent.OnChanges], ...}). Class({ onChanges: function() {...} }); After // Dart @Component({...}) class MyComponent implements OnChanges { void onChanges() {...} } // Typescript @Component({...}) class MyComponent implements OnChanges { onChanges(): void {...} } // ES5 var MyComponent = ng .Component({...}) .Class({ onChanges: function() { } });
This directory contains pure Dart packages that use standard pub layout.
Working with an existing package
- Run
gulp build.dart - Open the package in any Dart IDE of your choice
- Tada!
You do not need to rerun step 1 if you are only making changes in
modules_dart. However, you do need to run it again after you make a change
in modules. This is because these packages depend on code inside the dist
directory via dependency_overrides. Code in modules need to be transpiled
into dist before the IDE can "feel" your changes in modules.
Creating a new package
- Create a new directory with its own
pubspec.yamland standard pub layout. - Add both a normal dependency on
angular2and adependency_overrides, like this:
version: 0.0.0
dependencies:
angular2: '0.0.0'
dependency_overrides:
angular2:
path: ../../dist/dart/angular2
The publishing script will automatically rewrite version numbers, so use
0.0.0 both for your package and angular2 version. Similarly, do not
include authors and homepage, as they will be auto-populated. However,
do provide description, name (prefixed with angular2_), dependencies,
and dev_dependencies.