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

Factor out code discovery to separate class #63

Open
apjanke opened this issue Mar 20, 2019 · 0 comments
Open

Factor out code discovery to separate class #63

apjanke opened this issue Mar 20, 2019 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@apjanke
Copy link
Owner

apjanke commented Mar 20, 2019

Put the code that does class/method/function discovery in a separate class. That way it'd be easy for doctest to copy it if they want it, and easier to test. Seems like this is going to be a need throughout Testify, since Octave’s methods() and meta.class aren’t currently up to the task of discovering everything we need. (Especially with the case of shadowed duck-punched methods for classes that are defined spread across multiple source directories.)

@apjanke apjanke added the enhancement New feature or request label Mar 20, 2019
@apjanke apjanke added this to the 0.5.0 milestone Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant