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 :shrug:) .
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? :thinking:
Moreover, to convince more quickly the teams and superiors, it would be nice to release the library in version 1.0.0. :rocket:
Hello,
We have been using your library for a very long time. Thanks again!
Recently, we migrated to
jestand naturally, we changed lib (tojest-marble) because we thought it was incompatible with jest (jasmine-marble :shrug:) .But after having different behaviors (
jest-marbledoesn't flush with thetoBeOservableand forces to calltoSatisfyOnFlushwhich subscribes a second time ...) and looking closer at this project and testing, it turns out that there is no dependency onjasmineand it is fully compatible withjest.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? :thinking:
Moreover, to convince more quickly the teams and superiors, it would be nice to release the library in version 1.0.0. :rocket: