-
Notifications
You must be signed in to change notification settings - Fork 61
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
Improve AST node initialization #469
Conversation
This is about #421 (comment) ? |
@spoenemann I had that in mind, but I added the |
const allTypes = collectedTypes.interfaces.map(e => e.name).concat(collectedTypes.unions.map(e => e.name)); | ||
const references = buildReferenceTypes(collectedTypes); | ||
const metaData = buildTypeMetaData(collectedTypes); | ||
const superTypeMap = buildSupertypeMap(collectedTypes); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: How are sub types handled in ast reflection?
For interface A extends B, C {}
will there be an entry for A
with all inherited mandatory entries from B
and C
?
9a70b19
to
11e5bb5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! 👍
8af1128
to
324686b
Compare
Solves three issues:
boolean
properties