Fix typescript error due to schema type #137
Merged
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.
Checklist
npm run test
andnpm run benchmark
and the Code of conduct
Description:
Schema type was changed in pull request #134. One of the available schema types was
ObjectSchema
fromfluent-json-schema
package. Sincefluent-json-schema
is a development dependency, we cannot use it for production codeNow, if we do not install
fluent-json-schema
manually, we will get the wrong type for schema, or an error if we use"skipLibCheck": false
in the typescript config fileAfter this fix, we can still use
fluent-json-schema
, but we will not get wrong type or error if this package is missing