Skip to content

feat: default to effect v4 when the installed effect can't be detected - #71

Merged
m9tdev merged 2 commits into
mainfrom
feat/effect-v4-default-detected
Oct 29, 2026
Merged

m9tdev merged 2 commits into
mainfrom
feat/effect-v4-default-detected

Conversation

@m9tdev

@m9tdev m9tdev commented Oct 29, 2026

Copy link
Copy Markdown
Owner

Effect v4 is the current stable line, so it becomes the fallback.

  • Installed effect 3 still gets v3 output and effect 4 gets v4 output; effectVersion still overrides. Only the fallback changes: when effect can't be resolved, or its version has no major, the generator now emits v4 instead of v3.
  • New tests/effectVersion.test.ts runs the built generator against fixture projects with effect 3, effect 4, an unparseable version, no effect, and an effectVersion override.
  • README: v4 first in the examples, the beta note is removed, and the fallback is documented as v4.

Installed effect 3 still gets v3 output and effect 4 gets v4 output; only
the fallback (effect not resolvable, or no major in its version) changes
from v3 to v4. Adds tests that run the generator against fixture projects
with effect 3, effect 4, an unparseable version and no effect installed.
@m9tdev
m9tdev merged commit e9504a7 into main Oct 29, 2026
3 checks passed
@m9tdev
m9tdev deleted the feat/effect-v4-default-detected branch October 29, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant