-
-
Notifications
You must be signed in to change notification settings - Fork 492
Schema: Add standardSchemaV1 API to Generate a Standard Schema
#4359
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
Merged
Conversation
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
🦋 Changeset detectedLatest commit: e69b12d The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
df7f007 to
d425963
Compare
standard API to Generate a Standard SchemastandardSchemaV1 API to Generate a Standard Schema
c7af09f to
fb6f9d8
Compare
84dea62 to
52160a6
Compare
8657cfb to
b563ce3
Compare
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 6, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 7, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 7, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 9, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 10, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Co-authored-by: Tim <[email protected]>
Merged
effect-bot
pushed a commit
that referenced
this pull request
Feb 12, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 12, 2025
Co-authored-by: Tim <[email protected]>
effect-bot
pushed a commit
that referenced
this pull request
Feb 13, 2025
Co-authored-by: Tim <[email protected]>
tim-smart
added a commit
that referenced
this pull request
Feb 14, 2025
Co-authored-by: Tim <[email protected]>
tim-smart
added a commit
that referenced
this pull request
Feb 14, 2025
Co-authored-by: Tim <[email protected]>
WestBearMethod
added a commit
to WestBearMethod/project-kaguya
that referenced
this pull request
Dec 10, 2025
Elysia では Effect.schema を用いて HTTP リクエスト、HTTP レスポンスを型安全にすることができる。 これによってテストで受け取る値も型安全に処理することができるようになる。 以下の URL でどのようにして Effect と Elysia を組み合わせるかを学んだ。 Effect-TS/effect#4359 また、Effect.runPromiseExit を用いることで Effect の成功型、失敗型をパターンマッチさせていることに注目したい。
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.
Returns a "Standard Schema" object conforming to the Standard Schema v1 specification.
This function creates a schema whose
validatemethod attempts to decode and validate the provided input synchronously. If the underlyingSchemaincludes any asynchronous components (e.g., asynchronous message resolutionsor checks), then validation will necessarily return a
Promiseinstead.Any detected defects will be reported via a single issue containing no
path.Example