Navigation Menu

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

Best way to support chaining #11

Closed
mgenereu opened this issue Nov 8, 2018 · 5 comments
Closed

Best way to support chaining #11

mgenereu opened this issue Nov 8, 2018 · 5 comments

Comments

@mgenereu
Copy link

mgenereu commented Nov 8, 2018

As an extension to #8 , I'd like to either document the magic methods with @method or replace them with real method calls. My IDE refuses to do code completion and other features until they're there or in the docblock. So my question is which of the two would @pierredup prefer. I always prefer real methods, even if auto-generated by a script, than more magic.

@mgenereu
Copy link
Author

mgenereu commented Nov 8, 2018

To clarify, I'd like to do a pull request but I need to know what you want me to code on this.

@mgenereu
Copy link
Author

@pierredup ?

@pierredup
Copy link
Member

I think the best would be to auto-generate the methods.
We already have a compile script to compile all the functions into a single file. Part of that script can be to create the methods on the _ class (it can be generated as a separate class or a trait)

@mgenereu
Copy link
Author

Thanks for your feedback. I'll get started on this.

@j-masci
Copy link

j-masci commented Apr 24, 2022

Did this ever get worked on? Some code completion on the global _ class would be nice.

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