Suggestion Backlog Slog, 2/29/2016

[RyanCavanaugh]

Leap Day Edition 🎉

• Typing Work
  • Library include directives #7156 Library include directives
  • Built-in support for UMD module definitions #7125 UMD module definitions
• Salsa-supporting work
  • Optional parameter with jsdoc does not be respected by salsa intellisense #6992 Use smarter type fallbacks in error cases
• Suggestions
  • Trailing Commas in Function Param Lists #7279 Trailing commas in argument lists
  • Suggestion: Add a "forceStrictMode" compiler option #7209 Add a "force strict mode" option
  • "duplicate identifier" error in js files produced by tsc #7077 Duplicate identifiers in namespace emit
  • Class properties doesn't inherit types from interface #7011 Apply interface types to implicit-any-declared class properties
  • Implicit Enum Duplicate Values #6864 Disallow implicitly duplicated enum values
  • Suggestion: non-nullable type #185 Non-nullable: confirm that this is committed?
  • Suggestion: Permit an implementing class to ignore private methods of the implementee class #471 Permit an implementing class to ignore private methods of the implementee class
  • Support type guards on property access expression #3812 Type guards on property access
  • tsc chokes on switches in --example=VALUE format #6758 Allow --name=value commandline switch format
  • Checking for void in logical operations #7256 Disallow void in truthyness positions
  • In JS, importing JSON should not give an error #7071 require of .json file
  • Disallow module keyword in new code where namespace could be used? #6808 Start a deprecation path for module

[mhegazy]

Library include (#7156)

• Two folders called “library” only one has a .d.ts, use that
• What if we found two different files for the same declaration file (e.g. node v2),
  • We should show an error if both have dependency on the same library but the files are different
• It should be an error when importing a package with ///?
• Modules should not use /// <reference path=“..” /> or ///<reference library=”..” />
• Add the compiler library folder to the search path, e.g. ///<reference library=”es6.promise.d.ts” />
• Should I specify the path, or just the name of the library?
  • The library name seems much better
• Guidance for package authors:
  • What about typing dependencies for a package
  • Ship package without types, and ship a @typings\package separately
  • Ship types with package, and add “dependencies” on all your typings dependencies

UMD (#7125)

• More bike shedding 🚲 🏠 on the syntax, Built-in support for UMD module definitions #7125
  • new syntax options:
    export as namespace $;

[RyanCavanaugh]

The rest: out of 🕚