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

Don't allow :new if the mocked process is already a mock #26

Closed
paulo-ferraz-oliveira opened this issue Apr 12, 2022 · 0 comments · Fixed by #61
Closed

Don't allow :new if the mocked process is already a mock #26

paulo-ferraz-oliveira opened this issue Apr 12, 2022 · 0 comments · Fixed by #61
Milestone
1.0.0

Comments

@paulo-ferraz-oliveira
Copy link
Contributor

We're thinking this might prevent a category of issues, but don't want to implement it now before we get a good feeling of what it means.
@paulo-ferraz-oliveira paulo-ferraz-oliveira added this to the whenever milestone Apr 12, 2022
@paulo-ferraz-oliveira paulo-ferraz-oliveira changed the title Don't allow :new if the mocked process is already a mock Don't allow :new if the mocked process is already a mock May 15, 2022
@paulo-ferraz-oliveira paulo-ferraz-oliveira modified the milestones: whenever, 1.0.0 Nov 1, 2023
Merged
2 tasks
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
None yet
Milestone
1.0.0
Development

Successfully merging a pull request may close this issue.

Return {error, already_mocked} when using new/1,2 over mock 2Latinos/nuntius
1 participant
@paulo-ferraz-oliveira