Conversation
00ef920 to
38818a7
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
type Foo = { ... }now fully supported as an equivalent tointerface Foo { ... }for defining object shapes — including method signatures, which were previously silently dropped from type aliases in both parserstypesyntax in all examples (README, fetch, json, object, classes, features)Changes
Parser fixes (
src/parser-native/transformer.ts,src/parser-ts/transformer.ts):type Foo = { method(): void }— method signatures in type aliases now parsed and registered, matchinginterfacebehaviorTests (
tests/fixtures/interfaces/):type-alias-object.ts— nested type alias accesstype-alias-json-parse.ts—JSON.parse<T>()with a type aliastype-alias-optional.ts— optional fields in type aliasesTest plan
npm test)type Foo = { ... }works interchangeably withinterface Foo { ... }for field access,JSON.parse<T>(), optional fields, and method signatures