-
Notifications
You must be signed in to change notification settings - Fork 365
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
Move constants to settings.py
#993
Comments
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 4, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 4, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 4, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 5, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 5, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 5, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 5, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 10, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 13, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 14, 2019
Carson-Tang
added a commit
to Carson-Tang/site
that referenced
this issue
Oct 14, 2019
Xyene
pushed a commit
that referenced
this issue
Oct 20, 2019
malbareda
pushed a commit
to malbareda/JOEL-web
that referenced
this issue
Jan 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently constants are accessed as
getattr(settings, SETTING_NAME, SETTING_DEFAULT)
.This leads to a lot of hardcoding of
SETTING_DEFAULT
, as well as unnecessarily long code that could be avoided if these constants and their default values were instead added tosettings.py
.The text was updated successfully, but these errors were encountered: