feat(typescript-effect-schema): support effect@^3.10.0 #2659
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.
Context (-, typescript-effect-schema)
Input Format: -
Output Language: typescript-effect-schema
Description
With the effect v3.10.0 release, effect-schema became a stable version within the core
effect
package and@effect/schema
should not be used anymore as newer effect versions are incompatible with it.It already had the issue with the
Schema.Record
API moving fromSchema.Record(key, value)
toSchema.Record({key, value})
this PR addresses that one as wellCurrent Behaviour / Output
quicktype currently supports the usage of
@effect/[email protected]
to generate the schemas which is deprecated as now effect/schema is part of the coreeffect
library.Proposed Behaviour / Output
Solution
Changed import to use
effect
instead of@effect/schema
for the imports and fixed the behaviour of RecordsAlternatives
No Alternatives
Context