skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(): Dartanalyzer running.

Browse Source
This commit is contained in:
Hans Larsen
2016-01-29 14:01:19 -08:00
parent f1a6ed38fa
commit 813ae4df67
5 changed files with 55 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dart/writing-compatible-typescript.md
+1 -1
View File
@@ -37,4 +37,4 @@ Here's a list of gotchas to keep in mind when writing TypeScript code that will
* **Boolean expressions are required to be boolean.** There's no type coercion or truthiness concept in Dart. Code like this: `if (!aNumber) {}` must be refactored to be `if (aNumber != 0) {}`.
* **Accessing any platform primitive must be done through a Facade.** For example, Promises or DOM manipulation. Facades are going to be provided on a need-to-have basis.
* **Union types are a no-go.** Dart has them on its roadmap, but for now we must avoid them.
* **Dart files cannot have the same name as a reserved keyword.** For example, `for.dart`, `switch.dart` or `class.dart` are all invalid names. Since the TypeScript files have the same name when transpiled to Dart, they also have the same restriction.
* **Dart files cannot have the same name as a reserved keyword.** For example, `for.dart`, `switch.dart` or `class.dart` are all invalid names. Since the TypeScript files have the same name when transpiled to Dart, they also have the same restriction.