chore(deps): update dependency effect to v3.10.16 #3074
Merged
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 contains the following updates:
3.10.15
->3.10.16
Release Notes
Effect-TS/effect (effect)
v3.10.16
Patch Changes
#3918
4dca30c
Thanks @gcanti! - Use a specific annotation (AutoTitleAnnotationId
) to add automatic titles (added byStruct
andClass
APIs), instead ofTitleAnnotationId
, to avoid interfering with user-defined titles.#3981
1d99867
Thanks @gcanti! - Stable filters such asminItems
,maxItems
, anditemsCount
should be applied only if the from part fails with aComposite
issue, closes #3980Before
After
#3972
6dae414
Thanks @tim-smart! - add support for 0 capacity to Mailbox#3959
6b0d737
Thanks @gcanti! - RemoveOmit
from theClass
interface definition to align type signatures with runtime behavior. This fix addresses the issue of being unable to override base class methods in extended classes without encountering type errors, closes #3958Before
After
#3971
d8356aa
Thanks @gcanti! - Refactor JSON Schema Generation to Include Transformation Annotations, closes #3016When generating a JSON Schema, treat
TypeLiteralTransformations
(such as whenSchema.optionalWith
is used) as a special case. Annotations from the transformation itself will now be applied, unless there are user-defined annotations on the form side. This change ensures that the user's intended annotations are properly included in the schema.Before
Annotations set on the transformation are ignored. However while using
Schema.optionalWith
internally generates a transformation schema, this is considered a technical detail. The user's intention is to add annotations to the "struct" schema, not to the transformation.After
Annotations set on the transformation are now considered during JSON Schema generation:
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.