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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@effect/[email protected]
Minor Changes
#54
19e5a77
Thanks @mattiamanzati! - - Update internal version of effect from 2.x beta to 3.12.5#56
5b2b27c
Thanks @mattiamanzati! - Add support for Effect diagnosticsWith this release of the language service plugin, we aim to improve the overall Effect experience by providing additional diagnostics that tries to fix misleading or hard to read TypeScript errors.
All of the diagnostics provided by the language service are available only in editor-mode, that means that they won't show up when using tsc.
Diagnostics are enabled by default, but you can opt-out of them by changing the language service configuration and provide diagnostics: false.
Please report any false positive or missing diagnostic you encounter over the Github repository.
Missing Errors and Services in Effects
Additionally to the standard TypeScript error that may be cryptic at first:
you'll now receive an additional error:
Floating Effect
In some situation you may not receive any compile error at all, but that's because you may have forgot to yield your effects inside gen!
Floating Effects that are not assigned to a variable will be reported into the Effect diagnostics.
Used yield instead of yield*
Similarly, yield instead of yield* won't result in a type error by itself, but is not the intended usage.
This yield will be reported in the effect diagnostics.