nidus-sync/platform/email/job.go

package email

import (
	"context"

	"github.com/Gleipnir-Technology/bob"
	//"github.com/rs/zerolog/log"
)

func Job(ctx context.Context, txn bob.Executor, email_id int32) error {
	return sendEmailComplete(ctx, txn, email_id)
}
Overhaul email sending system Add logging and saving templates to the database for historical accuracy. 2026-01-23 20:36:16 +00:00			`package email`

			`import (`
			`"context"`

Create generic backend process, fix background interdependencies This refactor was born out of the inter-dependency cycles developing between the "background" module and just about every other module which was caused by the background module becoming a dependency of every module that needed to background work and the fact that the background module was also supposedly responsible for the logic for processing those tasks. Instead the "background" module is now very, very shallow and relies entirely on the Postgres NOTIFY logic for triggering jobs. There's a new table, `job` which holds just a type and single row ID. All told, this means that jobs can be added to the queue as part of the API-level or platform-level transaction, ensuring atomicity, and processing coordination is handled by the platform module, which can depend on anything. 2026-03-16 19:52:29 +00:00			`"github.com/Gleipnir-Technology/bob"`
			`//"github.com/rs/zerolog/log"`
Overhaul email sending system Add logging and saving templates to the database for historical accuracy. 2026-01-23 20:36:16 +00:00			`)`

Create generic backend process, fix background interdependencies This refactor was born out of the inter-dependency cycles developing between the "background" module and just about every other module which was caused by the background module becoming a dependency of every module that needed to background work and the fact that the background module was also supposedly responsible for the logic for processing those tasks. Instead the "background" module is now very, very shallow and relies entirely on the Postgres NOTIFY logic for triggering jobs. There's a new table, `job` which holds just a type and single row ID. All told, this means that jobs can be added to the queue as part of the API-level or platform-level transaction, ensuring atomicity, and processing coordination is handled by the platform module, which can depend on anything. 2026-03-16 19:52:29 +00:00			`func Job(ctx context.Context, txn bob.Executor, email_id int32) error {`
			`return sendEmailComplete(ctx, txn, email_id)`
Overhaul email sending system Add logging and saving templates to the database for historical accuracy. 2026-01-23 20:36:16 +00:00			`}`