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

Think about project name and version 1.0.0 #93

Open
kekel87 opened this issue Oct 17, 2022 · 0 comments
Open

Think about project name and version 1.0.0 #93

kekel87 opened this issue Oct 17, 2022 · 0 comments

Comments

@kekel87
Copy link

kekel87 commented Oct 17, 2022

Hello,

We have been using your library for a very long time. Thanks again!

Recently, we migrated to jest and naturally, we changed lib (to jest-marble) because we thought it was incompatible with jest (jasmine-marble 🤷) .

But after having different behaviors (jest-marble doesn't flush with the toBeOservable and forces to call toSatisfyOnFlush which subscribes a second time ...) and looking closer at this project and testing, it turns out that there is no dependency on jasmine and it is fully compatible with jest.

So, to avoid this kind of confusion in the future, to facilitate and boost the adoption of your lib, I think it would be interesting to find a better name for it? 🤔

Moreover, to convince more quickly the teams and superiors, it would be nice to release the library in version 1.0.0. 🚀

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

No branches or pull requests

1 participant