René's URL Explorer Experiment


Title: Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type · Issue #36348 · microsoft/TypeScript · GitHub

Open Graph Title: Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type · Issue #36348 · microsoft/TypeScript

X Title: Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type · Issue #36348 · microsoft/TypeScript

Description: Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type What? In TypeScript, when a class is created and bound to a name via a class declaration, the name can be used in both val...

Open Graph Description: Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type What? In TypeScript, when a class is created and bound to a name via a class decla...

X Description: Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type What? In TypeScript, when a class is created and bound to a name via a class d...

Opengraph URL: https://github.com/microsoft/TypeScript/issues/36348

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type","articleBody":"# Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type\r\n\r\n## What?\r\n\r\nIn TypeScript, when a class is created and bound to a name via a class declaration, the name can be used in both value and type positions. In contrast, when a class is bound to a name via `const`, `let`, or `var`, the name can only be used in value positions.\r\n\r\nI propose that when a class is bound to a name via `const`, `let`, or `var`, the name should be usable in both value and type positions, and that when such a name is used in a type position, it be interpreted as the instance type of the bound class value.\r\n\r\nMore formally:\r\n\r\n- A name should be deemed a _ClassValueName_ if:\r\n  - It is declared via a `const`, `let`, or `var` statement, and\r\n  - Its type is assignable to `new (...args: any[]) => any`, and\r\n  - Its type is not `any`\r\n- A _ClassValueName_ should be usable in any type position that a class declaration name could be used in, and\r\n- A _ClassValueName_ used in a type position should be interpreted as the instance type of the class value, in the same way that a class declaration name used in a type position is interpreted as the instance type of the class declaration\r\n\r\n### Examples of proposed behaviour\r\n\r\n```typescript\r\n// `Foo` is of type `new () => {}`\r\nconst Foo = class {};\r\n\r\n// `Foo` can be used in a type position here, and `foo` is of type `{}`\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n```typescript\r\n// `Foo` is of type `new \u003cT>(value: T) => { value: T }`\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n\r\n// `Foo` can be used in a type position here (and is generic), and `foo` is of type `{ value: number }`\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\n```typescript\r\nfunction newFooClass() {\r\n  return class \u003cT> { constructor(public value: T) {} };\r\n}\r\n\r\n// `Foo` is of type `new \u003cT>(value: T) => { value: T }`\r\nconst Foo = newFooClass();\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\n```typescript\r\nconst classes = {\r\n  Foo: class \u003cT> { constructor(public value: T) {} }\r\n};\r\n\r\n// `Foo` is of type `new \u003cT>(value: T) => { value: T }`\r\nconst { Foo } = classes;\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\n```typescript\r\nconst withBrand =\r\n  \u003cB extends string>(brand: B) =>\r\n    \u003cC extends new (...args: any[]) => {}>(ctor: C) =>\r\n      class extends ctor {\r\n        brand: B = brand;\r\n      };\r\n\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n// `FooWithBrand` is of type `new \u003cT>(value: T) => ({ value: T } & { brand: 'Foo' })`\r\nconst FooWithBrand = withBrand('Foo')(Foo);\r\n\r\n// `FooWithBrand` can be used in a type position here (and is generic), and `fooWithBrand` is of type `{ value: number } & { brand: 'Foo' }`\r\nconst fooWithBrand: FooWithBrand\u003cnumber> = new FooWithBrand(42);\r\n```\r\n\r\n## Why?\r\n\r\n### Unlike a class declaration, a class value requires a separate type declaration to expose the class's instance type\r\n\r\nFor class declarations, we can simply use the name of the class in a type position to reference its instance type:\r\n\r\n```typescript\r\nclass Foo {}\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\nBut for class values, a separate type declaration is required:\r\n\r\n```typescript\r\nconst Foo = class {};\r\n\r\ntype Foo = InstanceType\u003ctypeof Foo>;\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\nRequiring a separate type declaration has a few issues:\r\n\r\n- It's inconsistent with class declarations (which don't require a manual type declaration)\r\n- It doesn't work for generic classes (see next section)\r\n- It's boilerplate (which adds up, especially with multiple classes in the same file)\r\n\r\nWith this proposal however, we wouldn't need a separate type declaration, and all of the following would just work:\r\n\r\n```typescript\r\nconst Foo = class {};\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n```typescript\r\nfunction newFooClass() { return class {}; }\r\n\r\nconst Foo = newFooClass();\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n```typescript\r\nconst classes = { Foo: class {} };\r\n\r\nconst { Foo } = classes;\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n### There is currently no way to access the generic instance type of a generic class value\r\n\r\nNone of the following work:\r\n\r\n```typescript\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n// => Error: 'Foo' refers to a value, but is being used as a type here.\r\n```\r\n\r\n```typescript\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n\r\ntype Foo = InstanceType\u003ctypeof Foo>;\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n// => Error: Type 'Foo' is not generic.\r\n```\r\n\r\n```typescript\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n\r\ntype Foo\u003cT> = InstanceType\u003ctypeof Foo\u003cT>>;\r\n// => Error: '>' expected.\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\n```typescript\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n\r\ntype Foo\u003cT> = InstanceType\u003ctypeof Foo>\u003cT>;\r\n// => Error: ';' expected.\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\nWith this proposal however, we could simply use the name of the class value in a type position to reference its generic instance type:\r\n\r\n```typescript\r\nconst Foo = class \u003cT> { constructor(public value: T) {} };\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n// => No error\r\n```\r\n\r\n### It enables a potential workaround for [#4881](https://github.com/microsoft/TypeScript/issues/4881)\r\n\r\nThis doesn't work:\r\n\r\n```typescript\r\nconst withBrand =\r\n  \u003cB extends string>(brand: B) =>\r\n    \u003cC extends new (...args: any[]) => {}>(ctor: C) =>\r\n      class extends ctor {\r\n        brand: B = brand;\r\n      };\r\n\r\n@withBrand('Foo')\r\nclass FooWithBrand\u003cT> {\r\n  constructor(readonly value: T) {}\r\n}\r\n\r\ntype FooBrand\u003cT> = FooWithBrand\u003cT>['brand'];\r\n// => Error: Property 'brand' does not exist on type 'FooWithBrand\u003cT>'.\r\n```\r\n\r\nBut with this proposal, we could do this:\r\n\r\n```typescript\r\nconst withBrand =\r\n  \u003cB extends string>(brand: B) =>\r\n    \u003cC extends new (...args: any[]) => {}>(ctor: C) =>\r\n      class extends ctor {\r\n        brand: B = brand;\r\n      };\r\n\r\nconst FooWithBrand = withBrand('Foo')(\r\n  class \u003cT> {\r\n    constructor(public value: T) {}\r\n  }\r\n);\r\n\r\ntype FooBrand\u003cT> = FooWithBrand\u003cT>['brand'];\r\n```\r\n\r\nWhile this wouldn't be type support for actual decorators, it would at least provide _a_ means of class decoration that's reflected at the type level.\r\n\r\n### Flow supports this (there is prior art)\r\n\r\nThe following all work in Flow:\r\n\r\n```typescript\r\nconst Foo = class {};\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n```typescript\r\nconst Foo = class \u003cT> {\r\n  value: T;\r\n  constructor(value: T) { this.value = value; }\r\n};\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(12);\r\n```\r\n\r\n```typescript\r\nfunction newFooClass() { return class {}; }\r\n\r\nconst Foo = newFooClass();\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n```typescript\r\nfunction newFooClass() {\r\n  return class \u003cT> {\r\n    value: T;\r\n    constructor(value: T) { this.value = value; }\r\n  };\r\n}\r\n\r\nconst Foo = newFooClass();\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\n```typescript\r\nconst classes = { Foo: class {} };\r\n\r\nconst { Foo } = classes;\r\n\r\nconst foo: Foo = new Foo();\r\n```\r\n\r\n```typescript\r\nconst classes = {\r\n  Foo: class \u003cT> {\r\n    value: T;\r\n    constructor(value: T) { this.value = value; }\r\n  }\r\n};\r\n\r\nconst { Foo } = classes;\r\n\r\nconst foo: Foo\u003cnumber> = new Foo(42);\r\n```\r\n\r\nWhile feature parity with Flow is obviously not one of TypeScript's goals, Flow supporting this behaviour means that there's at least a precedent for it.\r\n\r\n## Why not?\r\n\r\n### It _may_ be a breaking change\r\n\r\nDepending on the implementation approach, this may be a breaking change.\r\n\r\nFor example, if this proposal were to be implemented by having the compiler automagically generate a separate type name whenever it encountered a _ClassValueName_, the generated type name may clash with an existing type name and break that currently working code.\r\n\r\nOn the other hand, if it were possible to implement this proposal using some kind of fallback mechanism (such as preferring any existing type name over using a _ClassValueName_ in a type position, for instance), then the change would be backwards compatible.\r\n\r\nIt is currently unclear whether or not the proposed change can be implemented in a backwards compatible manner.\r\n\r\n### It \"muddies\" the separation between the value and type namespaces\r\n\r\nTypeScript maintains separate namespaces for values and types. While this separation is fairly core to the language, there are already several exceptions in the form of class declarations, enums, and namespaces.\r\n\r\nThis proposal would introduce a new exception to that separation. This exception is particularly notable, as it would mark the first time a `const`, `let`, or `var`-declared name would be permitted in a type position. This is in contrast to all current exceptions, which each have construct-specific declaration syntax that differentiates them from standard variable declarations.\r\n\r\nThis proposal's \"muddying\" of the separation between the value and type namespaces may be confusing and/or surprising for both new and existing TypeScript users.\r\n\r\n## Next steps\r\n\r\n- [ ] Get feedback from both the TypeScript team and the community\r\n- [ ] Investigate potential implementation strategies\r\n\r\n## Checklist\r\n\r\nMy suggestion meets these guidelines:\r\n\r\n* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code (**unclear at this stage**)\r\n* [x] This wouldn't change the runtime behavior of existing JavaScript code\r\n* [x] This could be implemented without emitting different JS based on the types of the expressions\r\n* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)\r\n* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).\r\n","author":{"url":"https://github.com/treybrisbane","@type":"Person","name":"treybrisbane"},"datePublished":"2020-01-22T09:23:25Z","url":"https://github.com/microsoft/TypeScript/issues/36348"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:fd574218-66cd-836a-a8c8-7064c8bb57a9
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idBA46:882E2:93947D:C519D3:6B00E112
html-safe-nonce30eda73d0bda5b859d07279994d1288275140655503632d41a22d9233fa1a1ae
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQTQ2Ojg4MkUyOjkzOTQ3RDpDNTE5RDM6NkIwMEUxMTIiLCJ2aXNpdG9yX2lkIjoiMTkzOTI2MTQ2MjAzMTY4Nzk1NCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmacecf4bd4dcd3e9037695d29eda07f121acab300d3501810795f7cfb21068731df
hovercard-subject-tagissue:553410230
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/TypeScript/36348/issue_layout
twitter:imagehttps://opengraph.githubassets.com/adf975d418180aafce3c2aac6549f70e80ea7c4462946f142ac098cf097784c9/microsoft/TypeScript/issues/36348
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/adf975d418180aafce3c2aac6549f70e80ea7c4462946f142ac098cf097784c9/microsoft/TypeScript/issues/36348
og:image:altProposal: Allow a name bound to a class value to be used in a type position to reference the class's instance type What? In TypeScript, when a class is created and bound to a name via a class decla...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernametreybrisbane
hostnamegithub.com
expected-hostnamegithub.com
None27088b6977484d0d3321d9a11c907c6d6637b315cfa359ef7952dbf6292f9b14
turbo-cache-controlno-preview
go-importgithub.com/microsoft/TypeScript git https://github.com/microsoft/TypeScript.git
octolytics-dimension-user_id6154722
octolytics-dimension-user_loginmicrosoft
octolytics-dimension-repository_id20929025
octolytics-dimension-repository_nwomicrosoft/TypeScript
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id20929025
octolytics-dimension-repository_network_root_nwomicrosoft/TypeScript
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release624179fb8b88d26ba5bba08894eb60a1c5a1d93d
ui-targetcanary-1
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/microsoft/TypeScript/issues/36348#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTypeScript%2Fissues%2F36348
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTypeScript%2Fissues%2F36348
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=microsoft%2FTypeScript
Reloadhttps://github.com/microsoft/TypeScript/issues/36348
Reloadhttps://github.com/microsoft/TypeScript/issues/36348
Reloadhttps://github.com/microsoft/TypeScript/issues/36348
microsofthttps://github.com/microsoft
TypeScripthttps://github.com/microsoft/TypeScript
Codehttps://github.com/microsoft/TypeScript
Issues5k (5k)https://github.com/microsoft/TypeScript/issues
Pull requests309 (309)https://github.com/microsoft/TypeScript/pulls
Actionshttps://github.com/microsoft/TypeScript/actions
Projectshttps://github.com/microsoft/TypeScript/projects
Wikihttps://github.com/microsoft/TypeScript/wiki
Security and qualityhttps://github.com/microsoft/TypeScript/security
Insightshttps://github.com/microsoft/TypeScript/insights
https://github.com/microsoft/TypeScript
New issuehttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/36348
New issuehttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/36348
Proposal: Allow a name bound to a class value to be used in a type position to reference the class's instance typehttps://github.com/microsoft/TypeScript/issues/36348#top
In DiscussionNot yet reached consensushttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22In%20Discussion%22
SuggestionAn idea for TypeScripthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Suggestion%22
https://github.com/treybrisbane
Trey Brisbane (treybrisbane)https://github.com/treybrisbane
on Jan 22, 2020https://github.com/microsoft/TypeScript/issues/36348#issue-553410230
#4881https://github.com/microsoft/TypeScript/issues/4881
TypeScript's Design Goalshttps://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals
Ryan Cavanaugh (RyanCavanaugh)https://github.com/RyanCavanaugh
In DiscussionNot yet reached consensushttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22In%20Discussion%22
SuggestionAn idea for TypeScripthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Suggestion%22
on Jan 23, 2020https://github.com/microsoft/TypeScript/issues/36348#event-2974689017
https://github.com/RyanCavanaugh
Ryan Cavanaugh (RyanCavanaugh)https://github.com/RyanCavanaugh
on Jan 23, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-577796138
https://github.com/treybrisbane
Trey Brisbane (treybrisbane)https://github.com/treybrisbane
on Jan 25, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-578361915
https://github.com/ferk6a
Fernando Kiotheka (ferk6a)https://github.com/ferk6a
on Feb 19, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-587995391
Playgroundhttps://www.typescriptlang.org/play/#code/MYGwhgzhAEBCkFMDC4rQN4Cho+pgvppgC4CeADgtEgPYB2ExATgK7DE1MA8AKtALwZ8APgHQ6CAO4AKAHTywTAOYQAXNDB1SAbQC6ASgGieAbiIAzFnXYBLetCUJiAWVK0aIFJAi9oCAB7ECHQAJjC0DMxsHEzC0gBGiOo8hli40ExOLEx00KDefoHBYdCJEFRY2LiEhJjA9IzQru6eqDCCji5uNB5eUNLw5X0Q+kQ2dEFM5mDAVK4AkhMIUzMVVTj+6oPIbevQpOrNPa3eBEA
Playgroundhttps://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=20&pc=40#code/MYGwhgzhAEBCkFMDC4rQN4Cho+gWwE8AxAOwAoBKDaAJwQBcBXGk6AFmgF8BuTTzTPQIAHBNCQB7EhHo1GwehJoAeACrQAvBk4A+TdBIIA7mQB05sDQDmEAFzQwJAgG0AulQ17VvTADNGJAoAllLQEAwAsgSSEiAokBBq0AgAHvQIJAAmMJLSsvKKKvDh8VA6OmQARoj2qlRYuNDV4abCNBKKQqKmhKT6-oH0IayU1HRMLNAAzFy8-JigCdBRMXGoMKnpWTDFyOvU-OH0KxKxpRBkJ2frFAJBJOk0vmDAYlEAkg8ITy9iDbgpey7c7YXAEexXNYJPgCYBSCCxBCmEASKxkQxGOCIc6UHrEcgUW5w6SI5Gosjo4zLaKnKFQSgUPGkBlAA
https://github.com/trusktr
Joe Pea (trusktr)https://github.com/trusktr
on Aug 9, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-671107645
https://github.com/treybrisbane
Trey Brisbane (treybrisbane)https://github.com/treybrisbane
on Nov 13, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-726458650
Ryan Cavanaugh (@RyanCavanaugh)https://github.com/RyanCavanaugh
https://github.com/RyanCavanaugh
Ryan Cavanaugh (RyanCavanaugh)https://github.com/RyanCavanaugh
on Nov 13, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-726485675
Trey Brisbane (@treybrisbane)https://github.com/treybrisbane
https://github.com/RyanCavanaugh
Ryan Cavanaugh (RyanCavanaugh)https://github.com/RyanCavanaugh
on Nov 13, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-726486517
https://github.com/treybrisbane
Trey Brisbane (treybrisbane)https://github.com/treybrisbane
on Nov 13, 2020https://github.com/microsoft/TypeScript/issues/36348#issuecomment-726561438
Ryan Cavanaugh (@RyanCavanaugh)https://github.com/RyanCavanaugh
Martijn Walraven (martijnwalraven)https://github.com/martijnwalraven
on May 4, 2021https://github.com/microsoft/TypeScript/issues/36348#event-4682442504
Remove global types from `apollo-server-env`https://github.com/apollographql/apollo-server/commit/4159aa1651dae213dddcc5b60677643b2a46ea21
4159aa1https://github.com/apollographql/apollo-server/commit/4159aa1651dae213dddcc5b60677643b2a46ea21
David Glasser (glasser)https://github.com/glasser
on May 4, 2021https://github.com/microsoft/TypeScript/issues/36348#event-4684802248
Remove global types from `apollo-server-env`https://github.com/apollographql/apollo-server/commit/0ee74b6c11d5a049ecf8ff428f72a078033dd42a
0ee74b6https://github.com/apollographql/apollo-server/commit/0ee74b6c11d5a049ecf8ff428f72a078033dd42a
Upgrade TypeScript and typecheck testshttps://github.com/apollographql/apollo-server/commit/caa6093d5caf9627a1c434227d76d4d414c3be91
caa6093https://github.com/apollographql/apollo-server/commit/caa6093d5caf9627a1c434227d76d4d414c3be91
Upgrade TypeScript and typecheck testshttps://github.com/apollographql/apollo-server/commit/2d7e8e3f10681c0645e860b8a52d6e8f56f232c6
2d7e8e3https://github.com/apollographql/apollo-server/commit/2d7e8e3f10681c0645e860b8a52d6e8f56f232c6
Upgrade TypeScript and typecheck testshttps://github.com/apollographql/apollo-server/commit/39263a3db64e957d22774e43d48628016617d55a
39263a3https://github.com/apollographql/apollo-server/commit/39263a3db64e957d22774e43d48628016617d55a
Upgrade TypeScript and typecheck tests (#5165)https://github.com/apollographql/apollo-server/commit/b9dc920b26fbdb152016481401b745ae4e5fad44
#5165https://github.com/apollographql/apollo-server/pull/5165
b9dc920https://github.com/apollographql/apollo-server/commit/b9dc920b26fbdb152016481401b745ae4e5fad44
Trevor Scheer (trevor-scheer)https://github.com/trevor-scheer
on Feb 1, 2022https://github.com/microsoft/TypeScript/issues/36348#event-5991883768
Upgrade TypeScript and typecheck tests (#5165)https://github.com/apollographql/apollo-datasource/commit/6efa79073f0f663057368ffbf6058a8e3d1b2183
6efa790https://github.com/apollographql/apollo-datasource/commit/6efa79073f0f663057368ffbf6058a8e3d1b2183
https://github.com/lkj4
lkj4https://github.com/lkj4
on Feb 20, 2022https://github.com/microsoft/TypeScript/issues/36348#issuecomment-1046129945
Ryan Cavanaugh (@RyanCavanaugh)https://github.com/RyanCavanaugh
https://stackblitz.com/edit/typescript-1czz7l?file=index.tshttps://stackblitz.com/edit/typescript-1czz7l?file=index.ts
Sign up for freehttps://github.com/signup?return_to=https://github.com/microsoft/TypeScript/issues/36348
Sign in to commenthttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/36348
In DiscussionNot yet reached consensushttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22In%20Discussion%22
SuggestionAn idea for TypeScripthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Suggestion%22
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.