🤖 User test baselines have changed#26358
Merged
weswigham merged 1 commit intomicrosoft:masterfrom Aug 10, 2018
Merged
Conversation
typescript-bot
force-pushed
the
user-update-20180705
branch
from
0309e8f to
7810e9c
Compare
sandersn
approved these changes
Aug 10, 2018
Member
sandersn
left a comment
sandersn
left a comment
There was a problem hiding this comment.
I think these changes are fine as long as we don't have any fixes needed to make React work. @weswigham is that the case?
| index.tsx(63,9): error TS7031: Binding element 'handleChange' implicitly has an 'any' type. | ||
| index.tsx(64,9): error TS7031: Binding element 'handleBlur' implicitly has an 'any' type. | ||
| index.tsx(65,9): error TS7031: Binding element 'handleSubmit' implicitly has an 'any' type. | ||
| index.tsx(66,9): error TS7031: Binding element 'isSubmitting' implicitly has an 'any' type. |
Member
There was a problem hiding this comment.
Does this require a fix on our side? Or just a change to react? @weswigham
Member
There was a problem hiding this comment.
#26281 is half a fix for it (the intersection on the inside). There's also the string extends keyof P in the type that won't simplify, though; that'll need to be remodeled so it can somehow resolve even when P is still generic (or just be removed - passing string into all the Pick and friends calls is probably fine).
| node_modules/lodash/_cloneBuffer.js(4,69): error TS2339: Property 'nodeType' does not exist on type '{}'. | ||
| node_modules/lodash/_cloneBuffer.js(7,80): error TS2339: Property 'nodeType' does not exist on type '{ "../../../tests/cases/user/lodash/node_modules/lodash/_cloneBuffer": {}; }'. | ||
| node_modules/lodash/_cloneBuffer.js(4,69): error TS2339: Property 'nodeType' does not exist on type '(buffer: any, isDeep?: boolean | undefined) => any'. | ||
| node_modules/lodash/_cloneBuffer.js(7,80): error TS2339: Property 'nodeType' does not exist on type '{ "../../../tests/cases/user/lodash/node_modules/lodash/_cloneBuffer": (buffer: any, isDeep?: boolean | undefined) => any; }'. |
Member
There was a problem hiding this comment.
This is just an extra-error message bug, I discovered yesterday. So I think it's fine to accept this change.
errendir
added a commit
to errendir/TypeScript
that referenced
this pull request
Aug 11, 2018
* origin/master: (283 commits) Don't error on destructure of private property with computed property syntax (microsoft#26360) getDefaultExportInfo: Use `getImmediateAliasedSymbol` instead of `getAliasedSymbol` (microsoft#26364) review comments restore old algorithm Dont use baseURL relative absolute paths in declaration emit, use absolute paths in bundle emit (microsoft#26341) Update user baselines (microsoft#26358) Don't store @template constraint in a TypeParameterDeclaration node (microsoft#26283) fixAddMissingMember: Support interface and don't crash on type parameter (microsoft#25995) Don't include class getter in spread type (microsoft#26287) Don't crash on computed property in destructure (microsoft#26334) Check the ambientness of a symbol name before attempting to trim it (microsoft#26312) Still generate signatures in SkipContextSensitive mode just to match on return types (microsoft#25937) fix handling if there is no commonPrefix Actually add sorting of elaboration text to user baselines Ping ryan instead of mohammed for user PRs now handle failed lookups make it work for root directory really, really fix test(?) add test fix commonPrefix handling ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please review the diff and merge if no changes are unexpected.
You can view the build log here.
cc @weswigham @sandersn @RyanCavanaugh