JSDoc support in JavaScriptYou 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
Future wish list · Issue #5040 · eslint/eslint
We are almost ready to release 2.0.0, and as such, it's time to start thinking about 3.0.0. As usual, the goal of this issue is to gather feedback on important changes that would be breaking or ambitious. (Other suggestions can just be filed as an issue.) We are already looking at dropping support for Node < 4 in 3.0.0. One thing I'd like to hear is ideas for how can ESLint better support TypeScri
Suggestion Backlog Slog, 1/4/2016 · Issue #6347 · microsoft/TypeScript
First slog of 2016 🎉 Some old ones 👴 Removing the qualified name restriction on import targets #1166 Allow import of identifiers 'type' aliases of string can not be used as object index signature. #1778 Allow type aliases of strings to be index signature parameters Error messages are difficult to parse when class incorrectly implements an interface #1796 Reduce error noise when class incorrectly
Suggestion Backlog Slog, 2/1/2016 · Issue #6800 · microsoft/TypeScript
On the docket Destructuring causes error for null/undefined properties #6784 - Destructuring a property of an optional property should be an error Add separate compiler option for generated declarations output directory. #6723 - Allow separate outDir for declaration files Const numbers that index into tuples do not produce the correct type #6678 - Use const initializer to resolve tuple type indexi
Design Meeting Notes for 2/05/2016 · Issue #6930 · microsoft/TypeScript
Joke of the day Anders: "What do you call a fish without an eye?" "Fsh!" Breaking Changes "use strict" changes for modules (#3676) Requested by several people. Broke several people. New flag Yay, new flags! Today's flag is... emitNonStrictModules. Keeps compliance, but allows people to revert behavior. Do we emit "use strict" for classes? No. We should. Should this flag affect that when we make th
Design Meeting Notes for 1/29/2016 · Issue #6735 · microsoft/TypeScript
Different modifiers for get/set accessors (#2845) People want private/protected set accessors with public get accessors. Or combinations thereof. Why can't people use private backing fields with a readonly accessor? Because that's annoying. We'd need to add modifiers. "Modifier salad" Doesn't really give you the encapsulation that you wanted. "I meant public, but only to certain assemblies. Now yo
Design Meeting Notes, 2/12/2016 · Issue #7059 · microsoft/TypeScript
Implicit Index Signatures Implicit index signatures #7029 issue Why does { foo: T } not satisfy { [key:string]: T }? #6041 and many others logged in the past Longstanding pain point / confusion source e.g. see upvotes on http://stackoverflow.com/questions/22077023/why-cant-i-indirectly-return-an-object-literal-to-satisfy-an-index-signature-re Bad solution you might think of: Infer this all the tim
Built-in support for UMD module definitions · Issue #7125 · microsoft/TypeScript
where id is any Identifier. This is only legal as a top-level declaration a .d.ts file containing other top-level export declarations (e.g. export function, export var, export =, etc.). Multiple of these declarations may appear in the same file so long as they supply different identifiers. When the containing file is imported through import syntax, the declaration has no effect. When the containin
TypeScript extensibility · Issue #6508 · microsoft/TypeScript
TypeScript Extensibility This is an umbrella issue for tracking the design of an extensibility model for TypeScript. There have already been a number of issues opened with regards to supporting Angular2 via such a model, (especially for richer template editing support), so this will be the initial focus. This not only ensures rich support for a key TypeScript scenario, but by solving real problems
Proposal: Bundling TS module type definitions · Issue #4433 · microsoft/TypeScript
Relates to #3159, #4068, #2568, this branch, and this tool. Goals Bundle declarations for TS projects to allow a library to be consumed with a single TS file, despite being many modules internally. Because of complicated internal module dependencies which would rather not be exposed to the consumer, this should flatten the exported module types as best as it can. (Ideally, completely.) Proposal Wh
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Fix CommonJs modules by billti · Pull Request #7249 · microsoft/TypeScript
GitHub - mgechev/codelyzer at advanced
Lint nested ++ by sandersn · Pull Request #6212 · microsoft/TypeScript
Design Meeting Notes for 1/22/2016 · Issue #6614 · microsoft/TypeScript
Implicit index signatures by ahejlsberg · Pull Request #7029 · microsoft/TypeScript
Constructor Visibility by AbubakerB · Pull Request #6885 · microsoft/TypeScript
Abstract properties by sandersn · Pull Request #7184 · microsoft/TypeScript
Add separate compiler option for generated declarations output directory. · Issue #6723 · microsoft/TypeScript
UMD support by RyanCavanaugh · Pull Request #7264 · microsoft/TypeScript
Proposal: Run-time Type Checks · Issue #7607 · microsoft/TypeScript
