TS: Remove generated profile override interface#104
Merged
Conversation
The interface (e.g. `export interface USCoreBodyWeightProfile extends Observation`) declared narrowed fields directly on the profile type, but actual data lives in `this.resource`. This created a false expectation that fields like `profile.subject` exist on the instance. Profile narrowing is now expressed only through validation and class accessors.
ryukzak
changed the title
ryukzak
changed the title
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
1 participant
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.
generateProfileOverrideInterfaceand supporting functions (detectFieldOverrides,tsTypeForProfileField,collectDisallowedChoiceFields)FieldOverridestype andoverridesparam fromgenerateProfileImportsisSpecializationTypeSchema,typeSchemaInfo,resolvePrimitiveType,tsEnumType)The interface (e.g.
export interface USCoreBodyWeightProfile extends Observation { ... }) was misleading — actual data lives inthis.resource, not on the class instance, so the interface created wrong expectations.