Open apexDev37 opened 3 months ago
Cool. I'll take a look at it.
I have deployed a version of the app btw. It's still behind though. Check it out using this ip. http://13.201.95.101:8000/. I'm still working on it so you can experience some downtime
I have deployed a version of the app btw.
Hey @C-o-m-o-n, appears that the staging link is no longer valid(?)
Cool. I'll take a look at it.
If you haven't already started, I can take this up in my free time.
Cool. I'll take a look at it.
If you haven't already started, I can take this up in my free time.
Hello @apexDev37 - Kindly proceed. Sorry for the late recon. @C-o-m-o-n had missed this he is handling another issue.
Overview
Some models implement a denormalized field (ie.
<relation>_count
) to store the count value for a related model in the project. Currently, no tracking mechanism (increment or decrement) is implemented for all denormalized fields through one of the following project levels or scopes: endpoints, transactions, or asynchronous tasks.Intended Outcome
constituency_count
) (domain knowledge required. Kindly consult if unsure).IMO, this should preferably be at the transactional level, which adheres to the best practice of having fat models and thin views. This Django paradigm closely maps to a "rich domain model" for those from a DDD world. This can also be done asynchronously, but keep in mind this comes with additional complexity to set up, test, and maintain.
Note
CONTRIBUTING
docs after reading this.