-
Notifications
You must be signed in to change notification settings - Fork 121
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
Fix up from_query
docs
#822
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the time, we chose to require the parameters to avoid having two optional arguments that default to an empty list, which can be confusing.
Anyway, I am OK with merging this, your call!
Yeah I agree it can be confusing. Perhaps better to document it correctly instead of changing it? Or, could |
👍 for improving the docs too! |
DataFrame.from_query
DataFram.from_query
Okay I've made |
Actually, I am not the biggest fan of this approach, sorry. :( Params are allegedly very common (or should be due for security), so I think it should be more first class than an option. Maybe we can do this:
This way we can both as default but without the confusion? 🤔 |
Ah, I didn't know they should be encouraged. In that case, I think better to leave it as is but document it -- I'll do that. |
a82f577
to
00fe1a5
Compare
DataFram.from_query
from_query
docs
😅 Okay there. |
The examples for
DataFrame.from_query
showfrom_query/2
, but this isn't defined. Params need to be passed, even if empty.