Hey All, We've tested orbit `6.0.0` in our own pr...
# orbit-mvi
m
Hey All, We've tested orbit
6.0.0
in our own projects and gathered community feedback and realised upgrading to this version is pretty painful at the moment due to the fact all intent methods now have to return
Job
. This can be a huge refactoring pain if, like us, you're using interfaces to pass the ViewModel to the UI for example. We've submitted a PR for an API change for
6.1.0
that will allow you to expose `Job`s on a case by case basis as and when needed in tests, without the need to do this across the entire project. https://github.com/orbit-mvi/orbit-mvi/pull/193 In the meantime, I would hold off upgrading to
6.0.0
on that basis. I sincerely apologise to the community, especially if you'd already upgraded to
6.0.0
and had to do the extra work to refactor your projects. In the future, any large changes to Orbit will go through internal dogfooding on our own real world (commercial) projects before we create a release to make sure this does not happen again.
👍 3
🙏 2
g
No interfaces here, so it was a smooth update.
❤️ 1
a
Same here. Mostly smooth update. For us the most work was updating our tests to new pattern. But that’s all
🎉 1