- **status**: review --> closed
---
** [tickets:#8460] allow sending already-formatted message**
**Status:** closed
**Milestone:** unreleased
**Created:** Wed Sep 07, 2022 02:30 PM UTC by Dillon Walls
**Last Updated:** Fri Sep 09, 2022 06:24 PM UTC
**Owner:** Dillon Walls
We would like to
- **status**: open --> review
---
** [tickets:#8460] allow sending already-formatted message**
**Status:** review
**Milestone:** unreleased
**Created:** Wed Sep 07, 2022 02:30 PM UTC by Dillon Walls
**Last Updated:** Fri Sep 09, 2022 06:11 PM UTC
**Owner:** Dillon Walls
We would like to be
* I like `send_raw` -- renamed.
* Ah, the commit message is misleading by referencing task, I have force-pushed
with a new message. I didn't intend for `send_raw` to be a `@task`, but instead
something that a task could call. I moved the task logic elsewhere; into our
override code (in FC).
- **status**: review --> open
- **assigned_to**: Dillon Walls
- **Reviewer**: Dave Brondsema
- **Comment**:
- Maybe `send_raw` for the name?
- `@task` decorator would be good to mark it as a task, and make it more easily
callable as one
---
** [tickets:#8460] allow sending
- **summary**: add task to allow sending already-formatted message --> allow
sending already-formatted message
- Description has changed:
Diff:
--- old
+++ new
@@ -1 +1 @@
-We would like to be able to just add an email to the task queue with all of
the content/headers already determined.
