-
Notifications
You must be signed in to change notification settings - Fork 26
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
Return previous schema type #143
Open
klaseca
wants to merge
1
commit into
fastify:master
Choose a base branch
from
klaseca:return-previous-schema-type
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,6 +8,7 @@ import envSchema, { | |
} from '..'; | ||
import Ajv, { KeywordDefinition, JSONSchemaType } from 'ajv'; | ||
import { Static, Type } from '@sinclair/typebox'; | ||
import S from 'fluent-json-schema'; | ||
|
||
interface EnvData { | ||
PORT: number; | ||
|
@@ -24,6 +25,11 @@ const schemaWithType: JSONSchemaType<EnvData> = { | |
}, | ||
}; | ||
|
||
const schemaFluent = S.object().prop( | ||
'PORT', | ||
S.number().default(3000).required() | ||
); | ||
|
||
const schemaTypebox = Type.Object({ | ||
PORT: Type.Number({ default: 3000 }), | ||
}); | ||
|
@@ -41,15 +47,20 @@ expectType<EnvSchemaData>(envSchemaDefault()); | |
const emptyOpt: EnvSchemaOpt = {}; | ||
expectType<EnvSchemaOpt>(emptyOpt); | ||
|
||
const optWithSchemaFluent: EnvSchemaOpt = { | ||
schema: schemaFluent, | ||
}; | ||
expectType<EnvSchemaOpt>(optWithSchemaFluent); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, it can never be false, because you cast it to EnvSchemaOpt in line 50. |
||
|
||
const optWithSchemaTypebox: EnvSchemaOpt = { | ||
schema: schemaTypebox, | ||
}; | ||
expectType<EnvSchemaOpt>(optWithSchemaTypebox); | ||
|
||
const optWithSchemaWithType: EnvSchemaOpt<EnvData> = { | ||
const optWithSchemaWithType: EnvSchemaOpt = { | ||
schema: schemaWithType, | ||
}; | ||
expectType<EnvSchemaOpt<EnvData>>(optWithSchemaWithType); | ||
expectType<EnvSchemaOpt>(optWithSchemaWithType); | ||
|
||
const optWithData: EnvSchemaOpt = { | ||
data, | ||
|
@@ -105,11 +116,11 @@ expectError<EnvSchemaOpt>({ | |
}, | ||
}); | ||
|
||
const envSchemaWithType = envSchema({ schema: schemaWithType }); | ||
const envSchemaWithType = envSchema<EnvData>({ schema: schemaWithType }); | ||
expectType<EnvData>(envSchemaWithType); | ||
|
||
const envSchemaTypebox = envSchema<SchemaTypebox>({ schema: schemaTypebox }); | ||
expectType<SchemaTypebox>(envSchemaTypebox); | ||
|
||
expectType<KeywordDefinition>(keywords.separator) | ||
expectType<KeywordDefinition>(envSchema.keywords.separator) | ||
expectType<KeywordDefinition>(keywords.separator); | ||
expectType<KeywordDefinition>(envSchema.keywords.separator); |
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.
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.
Did you evaluate adding the fluent-schema's
JSONSchema
type?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.
I am not quite sure what you mean by that. Are you suggesting to add
JSONSchema
type fromfluent-json-schema
to union type for schema? If so, read description of this pull requestThere 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.
Hmm. object is not a very good type. Should use something like Record<string, any> or so.
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.
And to be honest i dont understand why we remove the generic type
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.
Because it is not compatible to different JSON schema library.
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.
I think you should read backstory of this pull request - #134 , #137 , #138 . I think it will become clear to you
As for
typescript
:Record<string, any>
andobject
are equal. Also, we can not useRecord<string, unknown>
type, because it will not work with interfaces (typescript playground)