Skip to content

[Transforms] Merge master 08/09 #10263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 276 commits into from
Aug 26, 2016
Merged

[Transforms] Merge master 08/09 #10263

merged 276 commits into from
Aug 26, 2016

Conversation

yuit
Copy link
Contributor

@yuit yuit commented Aug 10, 2016

No description provided.

Andy Hanson and others added 30 commits August 2, 2016 06:18
…he expression of each `ExpressionWithTypeArguments` is an `EntityNameExpression`.
This makes sure that a union type that includes a type parameter is
still usable as the actual type that the type guard narrows to.
When a property is declared in the constructor and on the prototype of
an ES6 class, the property's symbol is discarded in favour of the
method's symbol. That because the usual use for this pattern is to bind
an instance function: `this.m = this.m.bind(this)`. In this case the
type you want really is the method's type.
Previously it was using TypeFacts.All. But the constraint of an
unconstrained type parameter is actually {}.
Limit "type guards as assertions" behavior
Add a helper function `getOrUpdateProperty` to prevent unprotected access to Maps.
…types path resolution errors (#9867)

* Change the shape of the shim layer to support getAutomaticTypeDirectives

* Change the key for looking up automatic type-directives

* Update baselines from change look-up name of type-directives

* Add @CurrentDirectory into the test

* Update baselines

* Fix linting error

* Address PR: fix spelling mistake

* Instead of return path of the type directive names just return type directive names
The extra `else` caused a ton of test failures!
Don't allow properties inherited from Object to be automatically included in TSX attributes
* Treat namespaceExportDeclaration as declaration

* Update baselines

* wip - add tests

* Add tests

* Show "export namespace" for quick-info
Kanchalai Tanglertsampan and others added 23 commits August 22, 2016 09:15
Allow "typings" in a package.json to be missing its extension
…ypes

JSDoc supports null, undefined and never types
* Use ES7 term of ExponentiationExpression

* Update timeout for mac OS

* Address PR: add space
Unify representation of tuples and other generic types
Return non-JsDocComment children for syntactic classification
* Properly emit await expression with yield expression

* Add tests and update baselines

* Move parsing await expression into parse unary-expression

* Update incorrect comment
…ally-typed-type-parameters

Instantiate this for contextually typed type parameters
…-resolves-to-module

allowSyntheticDefaultImports resolves to modules instead of variables
# Conflicts:
#	Gulpfile.ts
#	Jakefile.js
#	src/compiler/binder.ts
#	src/compiler/checker.ts
#	src/compiler/core.ts
#	src/compiler/diagnosticMessages.json
#	src/compiler/emitter.ts
#	src/compiler/parser.ts
#	src/compiler/program.ts
#	src/compiler/types.ts
#	src/compiler/utilities.ts
#	src/harness/compilerRunner.ts
#	src/harness/harness.ts
#	src/harness/projectsRunner.ts
#	src/harness/unittests/jsDocParsing.ts
#	src/harness/unittests/transpile.ts
#	tests/baselines/reference/classExpressionES63.js
#	tests/webTestServer.ts
@rbuckton
Copy link
Contributor

@yuit can you take a look at the lint failure?

@yuit yuit merged commit a370908 into transforms Aug 26, 2016
@yuit yuit deleted the mergeMaster_08/09 branch August 26, 2016 22:51
@kpreisser
Copy link
Contributor

kpreisser commented Aug 27, 2016

Hi,
sorry if this this a wrong place to ask, but I have a question about the merge operation of this pull request. It seems this PR (and the previous, #10182) were merged as "squash" commit instead of a merge commit, which means instead of retaining the original commits and then having a "merge" commit that merges the two branches, there is a single commit (with one parent commit instead of two) which contains all the changes, and the git history does not include the individual commits that have been merged.

However, I would have expected this to use a normal merge commit, because e.g. now if I want to merge the transforms branch into the master branch, I get a lot of Conflicts due to the squash commit (and I expected that the transforms branch would eventually be merged into the master branch).

Can you give me some insight about this, @yuit, @rbuckton? Thank you!

@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Domain: Transforms Relates to the public transform API
Projects
None yet
Development

Successfully merging this pull request may close these issues.