AngularDart 8 Roadmap

[GZGavinZhao]

This is an incomplete list that I can think of on the top of my head, and I'll come back here to add more things. Feel free to suggest anything more!

For now, I don't expect there to be breaking changes in existing codebases that are using null safety.

• infra
  • Establish a commit message standard (melos?) (Setup melos #14).
  • Use new matcher dart-archive/mockito#52
• angular
  • Find out a new name to publish our forks (Rename forked packages for publishing on pub #8).
  • Re-enable all the skipped tests in _tests/ (most of them have been resolved) (Re-enable all the skipped tests in _tests/ #9).
  • Migrate codebase to 2.17 language features. Currently, we're only compatible with Dart 2.17.
  • Fix all the static analysis warnings. (refactor!: fixing all static analysis warnings #31)
  • (Optional) HTML template intellisense/autocompletion (nganalyzer).
  • (Optional) Investigate PostCSS integration for Tailwind CSS, etc.
  • (Optional) Investigate easy asset packaging.
  • (Optional) Investigate easy interop of npm packages and bundle them into the final JavaScript.
• angular_test
  • Static analysis regarding type inference in NgTestBed (NgTestBed can't infer type of createXXFactory() #5).
• angular_components
  • Nuke all the unnecessary branches and rename the entire package to ngcomponents.
  • Migrate to null safety (Null safety migration angular_components#35).
  • Fix all the static analysis warnings.
• site-angulardart
  • Update all examples to Angular 7/8.
  • (Optional) Drop Jekyll, use something else. Our tooling is getting old (e.g. grinder, jekyll-assets) and slow. We can even use AngularDart to write that whole website and use ngpuppeteer to pre-render it. Hugo. Verified that it is theoretically doable, design in progress. Work in progress: Migrate contents to new website website#9
• misc
  • (Optional) Consider writing another component library that is much easier to understand/imitate than angular_components? So far everything in the ecosystem is around Material Design. We can utilize existing Angular TS libraries to drastically reduce the work, such as ng-zorro.

[ykmnkmi]

Old pipes and animations in Component?

[ykmnkmi]

Can we also deprecate and remove ReflectiveInjector, bootstrapStatic, runAppLegacy and runAppLegacyAsync? How it would look.

[GZGavinZhao]

@ykmnkmi I'm okay with that. Feel free to send in a PR!

[insinfo]

@GZGavinZhao
Congratulations for your dedication to this project, I would particularly like to be contributing to this project but I haven't had the time. I deal with AngularDart projects on a day to day basis, but at the company where I work we still have a lot of projects stuck in AngularDart 6 and dart 2.12. I really appreciate the idea of not being stuck with AngularDart Components (MaterialDesign), I use a lot of custom components that make use of CSS Bootstrap.

[ykmnkmi]

@GZGavinZhao looking at the "Fix all static analysis warnings" and "constant_identifier_names" rule (152 cases), can I deprecate public members with names like this "OnPush" and replace them with new ones?

[GZGavinZhao]

@ykmnkmi No problem, go for it :)

[ykmnkmi]

@GZGavinZhao I thinks analyzer warnings task is done.
What you think about migrating all packages and tests to Dart 3 and analyzer 6?

[GZGavinZhao]

@GZGavinZhao I thinks analyzer warnings task is done. What you think about migrating all packages and tests to Dart 3 and analyzer 6?

@ykmnkmi Good idea! The only caution I would have is that if we migrate to Dart 3, we either have to remove non-null-safe support entirely, or find a way to disable/isolate it during testing. In my opinion, the 2nd option is more desirable, but I'm not sure how difficult it would be. If the 2nd option is not possible, then we will likely have to remove non-null-safety support from AngularDart.

Side note, Angular's runtime code is already theoretically compatible with Dart 3 as indicated by the Pub packages page and it seems that @jodinathan was able to get it working as well; the only potential blocker here is the Angular Compiler, as explained in the previous paragraph.

[ykmnkmi]

Currently, I'm bumping all package versions to the minimal version that has migrated to Dart 3.0 or the latest pre-3.0 version and fixing errors and analysis warnings.

For example:

# ngtest/pubspec.yaml
dependencies:
  collection: ^1.17.2
  # ...

dev_dependencies:
  build_runner: ^2.4.6
  build_test: ^2.2.0
  build_web_compilers: ^4.0.4
  test: ^1.24.4
  # ...

One package that is holding up migration is mockito, as I am waiting for it to update. It's a dev dependency in ngforms, ngrouter, and _tests.

[insinfo]

@ykmnkmi @GZGavinZhao

Is it possible to keep AngularDart 8 compatible with dart 2.18, 2.19 and 3?
I'm asking this because many of my projects are stuck on dart 2.18.x at the moment