Split up the djblets.db.fields module into submodules.
Review Request #9751 — Created March 6, 2018 and submitted
djblets.db.fields
was getting far too large to easily maintain, and
some upcoming work onRelationCounterField
was going to make that just
a bit harder. This change addresses this by splitting up the different
areas of responsibility into their own submodules.None of the actual code has changed, and this means the older fields are
still poorly documented. An upcoming change will address this and other
cleanups.
Djblets and Review Board unit tests pass.
Built the docs and made sure that the
djblets.db.fields
docs properly
linked to the appropriate submodule docs, without serving up its own
copies of the docs.
- Summary:
-
Split up the django.db.fields module into submodules.Split up the djblets.db.fields module into submodules.
- Description:
-
~ django.db.fields
was getting far too large to easily maintain, and~ djblets.db.fields
was getting far too large to easily maintain, andsome upcoming work on RelationCounterField
was going to make that justa bit harder. This change addresses this by splitting up the different areas of responsibility into their own submodules. None of the actual code has changed, and this means the older fields are
still poorly documented. An upcoming change will address this and other cleanups. - Testing Done:
-
Djblets and Review Board unit tests pass.
~ Built the docs and made sure that the
django.db.fields
docs properly~ Built the docs and made sure that the
djblets.db.fields
docs properlylinked to the appropriate submodule docs, without serving up its own copies of the docs.