feat: add promise success diagnostic - #460
Merged
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
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.
Summary
promiseInEffectSuccesscorrectness diagnostic for Effect v3 and v4Effect<A, E, R>success channels across runtime expressions and report nativePromisemembers, including unionsEffect<Promise<...>>annotations, return types, assertions, and success-producing generic argumentsExample
The diagnostic recommends representing the asynchronous work with
Effect.promiseorEffect.tryPromise. Strict Promise identity intentionally excludesPromiseLikeand arbitrary thenables.Validation
pnpm setup-repopnpm lintpnpm checkpnpm testCloses #405