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

Breaking change: explicitly import either asyncdispatch or chronos #11

Merged
merged 4 commits into from
Jan 9, 2024

Conversation

markspanbroek
Copy link
Member

Reorganizes the code into separate versions for asyncdispatch and
chronos so that we no longer have to rely on hard-to-maintain code
that implicitly works with both asyncdispatch and chronos.

This is a backwards incompatible change.

Reorganizes the code into separate versions for asyncdispatch and
chronos so that we no longer have to rely on hard-to-maintain code
that implicitly works with both asyncdispatch and chronos.

This is a backwards incompatible change.
@markspanbroek markspanbroek force-pushed the explicit-import-asyncdispatch-chronos branch from 039fc6b to 7bcc20b Compare December 21, 2023 09:23
@markspanbroek markspanbroek marked this pull request as ready for review December 21, 2023 13:45
@gmega
Copy link
Member

gmega commented Jan 5, 2024

I like it. Since asyncdispatch and chronosv3 are compatible, I was thinking we could've probably still have maintained backwards compatibility by importing the v3-compatible runAsync template when one imports asynctest/unittest and asynctest/unittest2 (and having an error on chronos v4), but I think breaking compatibility is actually warranted in this case and makes things simpler/clearer. So LGTM.

@markspanbroek markspanbroek merged commit db3d1e0 into main Jan 9, 2024
12 checks passed
@markspanbroek markspanbroek deleted the explicit-import-asyncdispatch-chronos branch January 9, 2024 10:40
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.

2 participants