-
Notifications
You must be signed in to change notification settings - Fork 344
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
[FEAT]: Remove all Django documentation in the project #1078
Comments
@AbhijithGanesh can you point to an example documentation string? |
'''
WSGI config for civiwiki project.
It exposes the WSGI callable as a module-level variable named ``application``.
For more information on this file, see
https://docs.djangoproject.com/en/1.8/howto/deployment/wsgi/
''' Code bits like this(it is meant for django 1.8 but we use 3.2) |
If you want, you can update the comments with more recent links. However, I don't think we should remove them. |
They're not relevant anymore right? I can update them as a part of documentation process! Would that be fine? I will add docstrings for this project and remove the Django 1.8 related strings? @brylie |
One thing worth noting is that Django code and conventions tend to stay relevant for many years. It might be good for us to revisit some of these older files to identify where the conventions have changed/improved, but that may be out of scope for this task.
Just change any links containing |
Will keep them on my mind. |
Description
There are documentation strings related to the project when it was created and it is better if we remove it since we've migrated from the original version
What should have happened?
No response
What browser(s) are you seeing the problem on?
No response
Further details
No response
The text was updated successfully, but these errors were encountered: