-
-
Notifications
You must be signed in to change notification settings - Fork 409
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
MAINT: rename query_target methods to query_object be consistent with the rest of the API #3217
Comments
Hi @bsipocz ! could you please expand on this issue? I mean, I am assuming we should rename the query_target method, which would be the method name we should use? |
I can see maybe it is query_object, isn't it? |
Yes, |
Also, if there is no objection to the rename, I can do this as part of my upcoming API cleanup and consolidating efforts. |
Similarly, |
Sure, you can do it but please, we should keep in mind backwards compatibility, so maybe we should include a warning in query_target and keep it for some time... |
Definitely. Any renaming should be done as deprecations that are being kept around for a long time (I would think at least a year, or maybe more) |
Sure! you can do it if you have time. If not, please let me know and I will include it in our planning. |
I've noticed the API inconsistency in
esa.hubble
andesa.jwst
to use the namequery_target
as opposed to what we do in the rest of the package.I suppose we could rename (with appropriately long deprecation for the old names) to make the API more consistent.
cc @jespinosaar
The text was updated successfully, but these errors were encountered: