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

change a bit the mock engine to allow extension... #826

Open
Grummfy opened this issue May 24, 2019 · 0 comments
Open

change a bit the mock engine to allow extension... #826

Grummfy opened this issue May 24, 2019 · 0 comments

Comments

@Grummfy
Copy link
Member

Grummfy commented May 24, 2019

I think we should change a bit the behavior on the mock.
For now, if we want to change the behavior of it, we need to do what the visibility extension do, replace the mock generator with a child class. This doesn't allow atoum to be extended multiple time or you need to deal with conflict of multiple extension doing the same.

Example, the extension that I have (not publish for this reason) about trait, is become a bit harder because of this reason. So did you have any idea how we can improve a bit our mock engine to allow theses change and make it extendable?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants