IJsonSchema.IObject for object literal expression.
#914
Conversation
This file contains 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
When object literal expression type being used instead of named object type, `typia` had enrolled it into the `IJsonComponents` considering as a named type with `__type` and `__type.o${number}`.
However, it seems not suitable for purpose of the JSON schema spec. Therefore, I've added new type `IJsonSchema.IObject` and assigned it into the JSON schema values when object literal expression type being used.
> What lilteral expression type means?
>
> ```typescript
> // NAMED TYPE
> export interface IMember {
> id: string;
> }
>
> // LITERAL EXPRESSION
> const member: { id: string };
> ```
samchon
force-pushed
the
features/json
branch
from
9ff73ef
to
5faad09
Compare
samchon
commented
Dec 30, 2023
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.
When object literal expression type being used instead of named object type,
typiahad enrolled it into theIJsonComponentsconsidering as a named type with__typeand__type.o${number}.However, it seems not suitable for purpose of the JSON schema spec. Therefore, I've added new type
IJsonSchema.IObjectand assigned it into the JSON schema values when object literal expression type being used.