-
Notifications
You must be signed in to change notification settings - Fork 14
Home
Welcome to angular_components
from the AngularDart community! The main purpose of this repository is to migrate angular_components
to null safety, making it compatible with the latest angular
. If you're wondering what the heck AngularDart is and what does it have to do with AngularTS, checkout the documentation site.
From now on, we will refer AngularDart as "Angular". We will explicitly say AngularTS when we mean it.
So, without further ado, here's our plan and how the repository is structured:
-
master
: just your normal master branch. -
compatible
: where work is done to make sureangular_components
is compatible with the latest Angular v7. The project board is here.compatible
gets merged intonull-safety
branch frequently, and after it is complete, it will be merged into themaster
branch. -
null-safety
: where migration to null safety happens. Project board can be found here. Because (as of current state), null safety migration will be done by hand and we don't need to touch any part that is causing incompatibility,compatible
branch will continuously merge intonull-safety
to prevent a merge hell in the end. - rest of the branches: from the original repo, kept for no particular reason.
Hence, compatible
will be first merged into master
to ensure we have a usable angular_components
, and after some hard work, null-safety
will then be merged into master
so that Angular devs can enjoy sound null safety!
Our first priority is to make sure that angular_components
is compatible with the latest Angular v7. See issues labeled compatible
, and pick one (or usually, part of it) up! No contribution is too small, and all great projects are built from small commits!
Issue #35 tracks this progress.
You are still welcome to migrate the code! Every commit to compatible
will get merged into null-safety
. So, as long as you frequently pull in the latest changes from your fork, the chances of you doing redundant work is pretty small, though not zero.
Currently there's a helper script that tells you how many files have been migrated (i.e. passed static analysis) and the location of those that still need some work. Run dart run grinder
to use it!
[WIP]