chore: update to effet 3.10

[titouancreach]

Effect has updated to 3.10 merging @effect/schema into effect main package.

https://effect.website/blog/effect-3.10

So this PR, remove @effect/schema, change the imports and update effect.

btw it deprecates: #710

[titouancreach]

pretty sure there is something to change here too:

resolvers/package.json

Line 211 in 37c3f78

"build:effect-ts": "microbundle --cwd effect-ts --globals @hookform/resolvers=hookformResolvers,react-hook-form=ReactHookForm,@effect/schema=EffectSchema,@effect/schema/AST=EffectSchemaAST,@effect/schema/ArrayFormatter=EffectSchemaArrayFormatter,@effect/schema/ParseResult=EffectSchemaArrayFormatter,effect/Effect=Effect",

[charlee-dev]

also, you can try to bump it to 3.10.2 instead, as they had another update last night

[akoenig]

@titouancreach I contributed a PR back to your fork with the update of the microbundle task and an update to the most recent version of Effect.

[titouancreach]

@akoenig great !! can you make a PR on my fork 🙃 So we don't loose the commit history
Thanks!!

[dudeofawesome]

I've created a PR to bring the last of my changes from #710 that didn't make it into this PR.

[titouancreach]

Thanks @dudeofawesome !

[akoenig]

Don't want to sound pushy, but is there any chance to get this PR merged? Effect is moving pretty fast and this PR is blocking me from updating to Effect 3.10 – I'm afraid of getting behind the schedule and therefore having a large migration effort in the future.

[titouancreach]

@akoenig I don't know if it helps, but this resolver only consist in two files, I simply copy pasted it to my code waiting for this PR to be merged, so my code don't stay behind

[dudeofawesome]

@akoenig I've also got a version based on my old PR published on NPM, which I've been using to keep up with Effect.

You can use it pretty seamlessly by simply updating your package.json to point to my package instead, allowing you to keep your imports the same.

{
  ...
  "dependencies": {
    "@hookform/resolvers": "npm:@dudeofawesome/[email protected]"
  }
}

[lauren-inato]

@bluebill1049 any idea when this will be released?

[jonathanpowers-storable]

Ah, so

• This repo uses semantic-release, which expects one changelog entry per commit
• The latest commit started with chore:
• The commits were squashed, leaving the final commit message as the only one seen by semantic-release

Led to semantic-release ignoring that commit

We need to push another commit that starts with one of the correct triggers like feat: or fix: for it to cut a new release. The content of the commit does not matter.

@bluebill1049 @vinassefranche Do you want me to come up with an insignificant commit that meets the above criteria, or is there some other way you'd like to handle this?

[vinassefranche]

@jonathanpowers-storable thanks for the detailed info!
I'm not a maintainer of the repo so I'm not sure I have my voice on this but if you can push a commit that would trigger the release of a new version, it would be amazing!

[github-actions]

🎉 This PR is included in version 3.10.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀