@effect/language-service 0.28.3 → 0.30.0

package/README.md

@@ -46,10 +46,12 @@ And you're done! You'll now be able to use a set of refactors and diagnostics th
 - Warn on leaking requirements in Effect services
 - Warn on Scope as requirement of a Layer
 - Warn on subsequent `Effect.provide` anti-pattern
+- Detect wrong `Self` type parameter for APIs like `Effect.Service` or `Schema.TaggedError` and similar 
 - Unnecessary usages of `Effect.gen` or `pipe()`
 - Warn when importing from a barrel file instead of from the module directly
 - Warn on usage of try/catch inside `Effect.gen` and family
 - Detect unnecessary pipe chains like `X.pipe(Y).pipe(Z)`
+- Warn when using `Effect.Service` with `accessors: true` but methods have generics or multiple signatures
 
 ### Completions
 
@@ -103,6 +105,10 @@ Few options can be provided alongside the initialization of the Language Service
 }
 ```
 
+### DiagnosticSeverty properties list
+
+The full list can be found in the [diagnostics](https://github.com/Effect-TS/language-service/tree/main/src/diagnostics) folder.
+
 ## Why do diagnostics not appear at compile time?
 
 TypeScript LSPs are loaded only while editing your files. That means that if you run `tsc` in your project, the plugin won't be loaded and you'll miss out on the Effect diagnostics.