Unhide methods in astroquery.gaia
- Dominant language
- Python
- Stars
- 791
- Forks
- 451
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 4
Description
E.g. currently we have `__query_object` that is called in both `query_object` and `query_object_async`, but kept inaccessible to look at from a python prompt. I see no reason for having all these three methods defined while the latter two only calls on the implementation in the first.
Instead, we should rename the hidden to `query_object_async`, and use the decorator to create the `query_object`, just as we do in the other modules.
Contributor guide
Research direction
Start in the astroquery.gaia module by locating __query_object, query_object, and query_object_async. Compare their structure with the corresponding methods in other modules, then verify that the implementation is renamed and the decorator exposes the synchronous method without retaining redundant wrappers. Done means the public methods remain functional and the hidden implementation is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100