Migrate event bridge to tsgo and strict Oxlint - #4
Merged
Conversation
…-oxlint # Conflicts: # package.json # pnpm-lock.yaml # pnpm-workspace.yaml
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
1 participant
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
it.effectWhy
CODE-369 requires a single Effect diagnostic path through Oxlint instead of duplicating diagnostics between TypeScript and the old Effect plugin. This also aligns local hooks and CI linting with the same strict configuration.
Impact
Developers now receive type-aware TypeScript and Effect diagnostics from
pnpm run lint. Warnings fail the lint gate, and the effective config contains no disabled rules or suppression overrides.Validation
pnpm run checkThe deploy-backed e2e test was not run locally.