Uh oh!
There was an error while loading. Please reload this page.
Configuration Inheritance - #9941
Conversation
a652517 to
8f036a7Compare8f036a7 to
167d318CompareSince Alex Eagle (@alexeagle) was concerned about editor support, I've manually tested this change within vscode - as expected, there are no changes required to vscode to make it work, you just drop in the new tsserver. 😉 Once this is merged and we do an LKG (so our |
Kenneth Brubaker (clavecoder)
commented
Jul 30, 2016
Can Basarat Ali Syed (@basarat) test this on atom-typescript? |
Wesley Wigham (weswigham)
commented
Jul 30, 2016
also, cc: Paul van Brenk (@paulvanbrenk) to review this and check that VS should also be fine with this change. |
| return result; | ||
| } | ||
| export function mapObject<T, U>(object: Map<T>, f: (key: string, x: T) => [string, U]): Map<U> { |
There was a problem hiding this comment.
jsdoc would be nice here, specifically calling out what happens when keys are mapped to the same key (looks like last one wins and earlier ones are discarded)
# Conflicts: # src/compiler/core.ts
Wesley Wigham (weswigham)
commented
Aug 30, 2016
Mohamed Hegazy (@mhegazy) Is there a reason multiple inheritance was undesirable? IMO, It was useful for mixing in a standard set of debug options into another config hierarchy to avoid duplication. |
Mohamed Hegazy (mhegazy)
commented
Aug 30, 2016
sorry should have explained that before making the change. We have discussed it int he last design meeting. ppl felt that multiple inheritance complicates things and would not be super useful. if there are requests later on, we could add it back. Here are the notes: #10566 |
Fixes#9876
Implements with the semantics proposed in that issue.