GAIA: new datalink retrieve types for DR4#3371
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3371 +/- ##
=======================================
Coverage 70.07% 70.07%
=======================================
Files 232 232
Lines 19893 19893
=======================================
Hits 13940 13940
Misses 5953 5953 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
078955e to
da4e32a
Compare
|
Dear @bsipocz we have found a minor issue in the last commit (a missing comma in the list of retrieve types). Should we open a new pull request? |
|
Ouch, I should not have just looked at it and merged. Yes, please open a follow up PR |
|
Puzzling how/why this wasn't picked up on with the style checker 😒 |
|
I guess the style checker allows for strings to be split on multiple lines without warning? |
|
After reading the documentation https://docs.python.org/3/reference/lexical_analysis.html#string-literal-concatenation , it looks like the strings were concatenated. |
|
Yes, syntactically that's what happened; we use this feature of python strings throughout the code base. It seems like a hard-to-see corner case that a style checker could catch, but since they're already primed to complain about too-long lines, they don't remark on it. |
|
Ahh, yes, I suppose you're right as it all was in a list. Then there is no other solution but avoiding doing reviews as a multitask activity while at SciPy :) |
…DL_DR4_retrieve_types GAIA: Fix minor issue in PR #3371
Dear astroquery team,
we would like to include the following new datalink retrieve types for the next Gaia Data Release 4 (DR4):
It is important to note that this change is backward compatible because the Datalink products associated with these retrieve types are new.
cc @esdc-esac-esa-int
jira: GAIASWRQ-39