History
The acl branch refactored the way we handle history.
Currently each application manage its history itself. This means :
- In
urls.py
a line dedicated to history like here; - The models which need history have to registered in
re2o/views.py
here.
I see several issues with this :
- Our URLs are rather inconsistent. To see the history of the instance
n
of the modelbar
in the applicationfoo
we query the urlfoo/history/bar/n
. It would be more consistent to queryhistory/foo/bar/n
; - We have to handle history in the
urls.py
of the application; - History is hidden in the re2o directory;
- We have to manually register every models in
re2o/views.py
, which is not obvious for a new developer.
What could we do ?
- to solve 1., 2. and 3., I think we could create a dedicated application;
- to solve 4. we could either look in the REGISTERED_APPS of
re2o/settings.py
or maybe trying to make something like Django admin (I am not sure how it works).