Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove redundant sample in once #306

Merged

Conversation

kireevmp
Copy link
Contributor

With effector@23 calling a derived Unit is an error, so a sample that guarded that behavior is no longer required.

@igorkamyshev
Copy link
Member

However, user without TS won't know that returned event is not callable.

I believe, we should preserve current behavior for such a case.

Copy link
Member

@zerobias zerobias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, you are right, trigger is already not callable without additional sample, it will be a runtime error. Thanks!

@zerobias zerobias merged commit 6238f7b into effector:release/v2 Nov 28, 2023
zerobias added a commit that referenced this pull request Nov 28, 2023
* Use effector 23 release candidate

* Remove forward calls

* Remove guard usage

* greedy: true -> batch: false

* remove fork(domain) usage

* Remove onlyChanges usage

* Use skipVoid: false

* use the same TS version, which is used for effector

* Comply with TS deprecations and cut unrelevant lib check

* Make empty operator work with full-void stores

* Use UnitTargetable

* Add skipVoid to maps and combines (#302)

* Add skipVoid

* Use skipVoid false

* Use latest rc

* Update tests to reflect fixed bug

* Remove test for derived event call - it is not supported anymore

* Update `and` tests

* Update `or` tests

* Remove controversial type tests

Strict check was expected for a valid case with partial match

* Remove type tests for domain or scope in source

* Update combine-events type tests

* Fix build

* Test types against dist

* Fix condition types

* Fix `{}` in `every` and `some` tests

* Fix `name` support in debounce

* Fix `spread` types

* Fix double debounce trigger (#303)

Co-authored-by: Victor Didenko <victord@setplex.com>

* Skip failing cases

* Add effector 23 support (#304)

* Update effector version

* Set range of supported effector versions

* Ensure that `and` and `or` will updated with scope

* Set effector version strictly to 23 (#305)

* fix(once): remove redundant sample as of effector v23 (#306)

* Fix ci issues (#307)

* Update cra integration

* Fix lockfile for node 16/18 ci

* Use non-strict peer deps in cra integration

* Update pnpm

* Update lockfile

* Update cra lockfile

* Update custom integration

* Reorder imports

---------

Co-authored-by: Dmitry <ribkatt@gmail.com>
Co-authored-by: Victor <yumaa.verdin@gmail.com>
Co-authored-by: Victor Didenko <victord@setplex.com>
Co-authored-by: Mikhail Kireev <29187880+kireevmp@users.noreply.github.com>
@kireevmp kireevmp deleted the fix/once-remove-redundant-sample branch November 28, 2023 10:28
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.

3 participants