Vishnu KS 139ebf387b support: Pass various realm functions as template context. ... We currently have code to calculate the value of realm_icon_url, admin_emails and default_discount in two diffrent places. With the addition of showing confirmation links it would become three. The easiest way to deduplicate the code and make the view cleaner is by doing the calculations in template. Alternatively one can write a function that takes users, realms and confirmations as arguments and sets the value of realm_icon_url, admin_emails and default_discount appropriately in realm object according to the type of the confirmation. But that seems more messy than passing the functions directly to template approach.		2019-10-21 16:52:46 -07:00
..
lib	billing: Change RealmAuditLog.event_type from str to int.	2019-10-06 15:55:56 -07:00
management	models: Migration of Message.pub_date to date_sent, part 2.	2019-10-05 19:01:34 -07:00
migrations	migrations: Remove unused imports.	2019-02-02 17:01:04 -08:00
tests	tests: setUp overrides should call super().setUp().	2019-10-19 17:27:01 -07:00
__init__.py	Create "analytics" app with activity reports.	2013-11-06 12:07:32 -05:00
models.py	analytics/zilencer/zproject: Remove unused imports.	2019-02-02 17:31:45 -08:00
urls.py	activity: Create interface for doing support operations.	2019-03-11 12:01:11 -07:00
views.py	support: Pass various realm functions as template context.	2019-10-21 16:52:46 -07:00