GitHub - sverweij/dependency-cruiser: Validate and visualize dependencies. Your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Boolean literal types and return type propagation for generators · Issue #2983 · microsoft/TypeScript
This suggestion has a few pieces: Implement boolean literal types for true and false, in a fashion similar to Singleton types under the form of string literal types #1003 Implement type guards for booleans. Essentially, control flow constructs like if-else, while, for, etc would be subject to a type guard if their guard expression is a boolean. Now we can update generators to have a next method th
Suggestion: Add the nameof compile-time operator to convert property and function names into strings · Issue #1579 · microsoft/TypeScript
I would like to see the nameof operator be considered for Typescript. This feature was just added to C# description, and it is an elegant solution to a common issue in Javascript. At compile time, nameof converts its parameter (if valid), into a string. It makes it much easier to reason about "magic strings" that need to match variable or property names across refactors, prevent spelling mistakes,
Design Meeting Notes, 5/10/2017 · Issue #15747 · microsoft/TypeScript
CheckJs feedback Inference failures and explicit type parameters also contextual type and jsdoc.. Type checking Javascript object literals is not open-ended in Maps #15618 @type should take precedence, should propagate contextual type cast syntax, add /** @type {number} */ syntax. no type args needed for now Use of JSDoc types: in member assignment: Type annotations are frequently ignored in --che
Implicit module import/export elision · Issue #2812 · microsoft/TypeScript
Current behavior The compiler today elides imports and exports that are types or not referenced in a value position in the body of the importing module. See spec sections section 11.2.5 and section 11.2.6 for more details. This has allowed for using the same syntax to import types and/or namespaces the same way values are imported. This has been convenient but has caused some problems: It has been
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - angular/ngo
"Cannot find type definition file for 'node'." for 2.4.1 · Issue #16772 · microsoft/TypeScript
Implementing DeepMerge · Issue #12769 · microsoft/TypeScript
tsickle/README.md at master · angular/tsickle
add Array.prototype.filter signature with type guard by maiermic · Pull Request #10916 · microsoft/TypeScript
Stricter generic signature checks by ahejlsberg · Pull Request #16368 · microsoft/TypeScript
Add support for literal type subtraction · Issue #12215 · microsoft/TypeScript
ngrx
tuple type don't check number of elements · Issue #5259 · microsoft/TypeScript
GitHubがデスクトップクライアントをElectronで再実装
JSDoc Does not Pick up Type imported using Require · Issue #14056 · microsoft/TypeScript
if a JSSpecialPropertyDeclaration has a JSDoc type, use it by rbuckton · Pull Request #15788 · microsoft/TypeScript
Covariant checking for callback parameters by ahejlsberg · Pull Request #15104 · microsoft/TypeScript
GitHub - microsoft/TypeScript-React-Starter: A starter template for TypeScript and React with a detailed README describing how to use the two together.
Type Checking JavaScript Files
