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.

Sign up for GitHub

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

Jump to bottom

Switch to @typestrong/ts-mockito #46

Closed
Markus-Ende opened this issue Feb 8, 2023 · 0 comments · Fixed by #49
Closed

Switch to @typestrong/ts-mockito #46

Markus-Ende opened this issue Feb 8, 2023 · 0 comments · Fixed by #49
Projects
ng-mockito

Comments

@Markus-Ende
Copy link
Member

There had been quite some discussion in NagRock/ts-mockito#212, because ts-mockito seems to not be maintained anymore.

It was forked in TypeStrong/ts-mockito (npm) hoping that it will be merged back into ts-mockito but this seems not to be happening. ts-mockito was last published 3 years ago.

I tried replacing ts-mockito with @typestrong/ts-mockito in a big repo without any issues. So I propose moving to @typestrong/ts-mockito as peer dependency.
@Markus-Ende Markus-Ende added this to new in ng-mockito via automation Feb 8, 2023
Markus-Ende added a commit that referenced this issue Feb 8, 2023
@Markus-Ende
feat(ng-mockito): switch to @typestrong/ts-mockito
cc2dbf4 
BREAKING CHANGE, see #46
@qupaya-bot qupaya-bot mentioned this issue Apr 11, 2024
Merged
ng-mockito automation moved this from new to done Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
ng-mockito
done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

switch to @typestrong/ts-mockito qupaya/ng-mockito
1 participant
@Markus-Ende