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
Make a view for seeing the content that would go into digest emails #9974
Comments
@timabbott do you consider digest page will be calculated and cached or calculated on fly? How about do this in SQL, not by using ORM? |
@zulipbot claim |
Adds "/digest/" endpoint for rendering content of digest email to the web. Fixes zulip#9974
Hello @zy964c, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days. You can reclaim this issue or claim any other issue by commenting Thanks for your contributions, and hope to see you again soon! |
Adds "/digest/" endpoint for rendering content of digest email to the web. Fixes zulip#9974
We had a request from folks in the FHIR community for a convenient way to see "hot topics", new users, and other details that we currently include in Zulip's digest emails feature (which has been stagnant for a long time, in part because it's annoying to develop on an email that's hard to trigger manually).
The first step for working on this is to create a view for seeing the digest data; this is better both for developing the digest emails feature as well as the use case for FHIR. I'm thinking we create a new /digest view, that can (for v1) use same janky template rendering logic as the digest emails.
To support this, we need to create a Django view function for
/digest
, that basically callshandle_digest_email
with an option to, rather than callingsend_future_email
at the end (to trigger the digest email), instead just renders the HTML template to the web.It should be possible to test this in a development environment, and then we can deploy to chat.zulip.org for further iteration.
The text was updated successfully, but these errors were encountered: