-
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
Changes from 4 commits
afaea0e
806189a
3e4208d
b4b3e6a
8f51524
62a6e82
1a28646
bfaa2ea
e1bb6cb
c451e3e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,9 +23,9 @@ | |
author = 'UBC Launch Pad' | ||
|
||
# The short X.Y version | ||
version = '1.0' | ||
version = '2.0' | ||
# 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 commentThe 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 commentThe 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 commentThe 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 |
||
|
||
|
||
# -- General configuration --------------------------------------------------- | ||
|
@@ -42,6 +42,10 @@ | |
'sphinx_autodoc_typehints', | ||
] | ||
|
||
# Config options for the extensions | ||
typehints_fully_qualified = True | ||
always_document_param_types = True | ||
|
||
# Add any paths that contain templates here, relative to this directory. | ||
templates_path = ['docs/_templates'] | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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 commentThe 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 commentThe reason will be displayed to describe this comment to others. Learn more. I doubt it. |
||
""" | ||
self.error = 'Please set the following env variables:\n' + \ | ||
'\n'.join(missing_config_fields) |
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")