-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
ESA_JWST-doc-update: actual examples in JWST module #2451
Conversation
b4f11d2
to
00022cb
Compare
Hi @bsipocz , we have only updated the documentation, without changing the code, it is necessary that we include a row in the changelog? or maybe we can merge this PR without this change? thanks in advance! |
Codecov Report
@@ Coverage Diff @@
## main #2451 +/- ##
=======================================
Coverage 62.92% 62.92%
=======================================
Files 133 133
Lines 17300 17300
=======================================
Hits 10886 10886
Misses 6414 6414 📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
No, we don't do changelog for docs or any non user facing internal changes. |
Then, if there are not any other comments, maybe we can merge this PR. |
52b9f6c
to
b534709
Compare
Thanks for your feedback @eerovaher , @keflavich , @bsipocz ! everything is now solved so, if you agree, we can merge this PR. |
Dear all, can we close this PR? |
I'm looking into this, I suppose vacation season means we're away from the keyboard from time to time (I certainly was away having some ⛰️ refill in the past few days) 😄 |
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.
I haven't yet gone into any nitpicking details but first wonder whether you would have the capacity to remove the doctest-skip-all
directive from the top to start running doctest on these code snippets?
After that removal you would need to add the .. doctest-remote-data:
for each and every code block, but hopefully that is all, as the examples are very freshly made I suppose they will pass running them as tests.
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.
I would say that fixing the ...
vs >>>
issues are the only thing that needs to be fixed for merging, everything else is nitpicking, or thinking out loudly, or suggesting for future improvements.
I would love to have this module's narrative docs doctested (as said in the previous comment), but that can be done in a new follow-up PR. I think it's likely enough to change all the .. code-block:: python
lines to .. doctest-remote-data::
, and maybe some tweaking is needed for the outputs and formatting, but I don't expect much complications. Anyways, we can do this gradually, e.g. merging this PR and do opt out into testing in a new PR.
Dear @bsipocz , I am so sorry, I did not know you were away... Of course, do not worry if you are still on holiday, I will solve the issues in the meantime... |
Ok, I think all the required changes have been applied. |
I went ahead and fixed the remaining issues, the main ones:
There are a lot of |
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.
Some examples have been temporarily skipped, otherwise, all of them pass the tests now.
Thanks @jespinosaar! |
That is because we currently don't have data, there will be public data after the ERO release on July, 13th, and then I will update the examples with real download. Many thanks for looking into this! |
Many thanks @bsipocz !! |
Dear astroquery team:
This PR aims to update the documentation in ESA JWST module with more actual examples. I hope it is simple to merge. Thanks in advance for your support!
cc @esdc-esac-esa-int