@mahendra Added a few comments, will add some more tomorrow. Some general comments: - With the risk of introducing feature creep, I think it would be good to have a one-off emailing feature in the scheduling UI to test what the report looks like. It would make it easier to test if email settings work correctly, and also check if the email report renders properly. - Another feature that would be valuable in the UI (not for this release, but later): Custom resolution (if a report looks better in some resolution other than that defined in `superset_config.py`), - Slightly outside the scope of this PR, but `EMAIL_NOTIFICATIONS` is defined twice in `config.py`, and is slightly misleading for the dry run feature (if I understood the code correctly, emails are not sent unless `EMAIL_NOTIFICATIONS` is set to True). I would perhaps add a specific debugging flag for email schedules that controls dry run that would be called `SCHEDULED_EMAIL_DEBUG_MODE` or something similar, as it's not directly related to regular email notifications.
[ Full content available at: https://github.com/apache/incubator-superset/pull/5294 ] This message was relayed via gitbox.apache.org for [email protected]
