-
Notifications
You must be signed in to change notification settings - Fork 6
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
docs: general formatting, fix links, cleanups, rewrites #554
Conversation
- Add links to types in internal reference - Change the unicode directional single-/double-quotes to ascii ones so that mac users aren't selectively favoured - Add even more documentation on less documented functions - Make factory documentation visible when it wasn't for so long - Rewrite segments of architecture because it no longer reflected the current state of the project - Reformat some names to make internal reference links possible Probably should be in separate commits. But they are all under the umbrella of general cleanup.
Codecov Report
@@ Coverage Diff @@
## master #554 +/- ##
=======================================
Coverage 93.81% 93.81%
=======================================
Files 47 47
Lines 2669 2669
Branches 361 361
=======================================
Hits 2504 2504
Misses 108 108
Partials 57 57
Continue to review full report at Codecov.
|
❤️ |
@@ -635,7 +639,8 @@ def refresh_helper(self, user_id) -> ResponseTuple: | |||
Ensure that the local team database is the same as GitHub's. | |||
|
|||
In the event that our local team database is outdated compared to | |||
the teams on GitHub, this command can be called to fix things. | |||
the teams on GitHub, this command can be called to fix these | |||
inconsistencies. |
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.
This likely ties into #490 in that we can't remove this command, as we'll always need something to forcibly bring everything in line
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.
Probably need to add a Deprecation Warning
whenever someone calls the command.
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.
Oh my point was I dont think we can deprecate it, ever, since we need some way to force a state sync (for example, to add new features - essentially a "migration")
# The full version, including alpha/beta/rc tags | ||
release = '1.0.0' | ||
release = '2.0.0' |
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.
do we even do releases?
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.
Good question. Actually, there is a slim chance that this would come back and bite us. Technically we do releases. We are currently on v2.1.0. I'm thinking that'd be one of the things we'd talk about in the meeting?
Gonna change this to better reflect, but right now docs are generated (and not saved) on master push, soooo rolling release.
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 dropped an item in the meeting notes - feel free to add stuff! https://docs.google.com/document/d/1KcH2l6nJKyHoCDe6v6Sl0cLWQWKQQmSLqk_kXvZUsRw/edit
@@ -118,7 +118,7 @@ def __init__(self, missing_config_fields): | |||
""" | |||
Initialize a new MissingConfigError. | |||
|
|||
:param: missing_config_fields List of missing config variables | |||
:param missing_config_fields: the missing config variables |
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.
is there a linter that can catch these documentation errors?
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 doubt it.
Co-authored-by: Robert Lin <[email protected]>
- set header of readme correctly so that it is picked up by sphinx - use links to make README slightly more readable
…ket2 into cheukyin699/update-docs
I just noticed. Good question. After a bit of read, I think it's safe to say that, yes, there is a way to override this. And no, it's not pretty. See 62a6e82. It involves creating a dummy header in rst that gets turned invisible by CSS. Normally you can center paragraphs using the The raw HTML is still necessary for centering the header up top. At least, some of it is. |
@cheukyin699 sadly, your approach in 62a6e82 doesn't work on GitHub :( that's why I made the entire top section raw HTML previously - so that it would work on GitHub as well (IMO this is a requirement) - how it should look |
@rob ahhh. Ohhhh. Welp, back to the drawing board. Might not be possible then. |
Let's leave that for another PR - can you revert 62a6e82 and I'll approve? |
Another option: .. raw:: html
<style>
h1:nth-of-type(2) {
display: none;
}
<style> But that would be way too hacky for me. |
@bobheadxi reverted |
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.
thank you!!!!
Created #555 as follow-up |
Details
that mac users aren't selectively favoured
current state of the project
View newly built docs here: https://rocket2.readthedocs.io/en/cheukyin699-update-docs/