Gleipnir/nidus-sync
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
nidus-sync/platform/text/job.go

26 lines
881 B
Go
Raw Normal View History

Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +00:00
package text
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
"fmt"
Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +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
"github.com/Gleipnir-Technology/bob"
"github.com/Gleipnir-Technology/nidus-sync/config"
"github.com/Gleipnir-Technology/nidus-sync/db/enums"
"github.com/Gleipnir-Technology/nidus-sync/platform/types"
Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +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, text_id int32) error {
return sendTextComplete(ctx, txn, text_id)
Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +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 ReportSubscriptionConfirmationText(ctx context.Context, destination types.E164, report_id string) error {
content := fmt.Sprintf("Thanks for submitting mosquito report %s. Text for any questions. We'll send you updates as we get them.", report_id)
origin := enums.CommsTextoriginWebsiteAction
err := sendTextBegin(ctx, *types.NewE164(&config.PhoneNumberReport), destination, content, origin, true, true)
Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +00:00
if err != nil {
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
return fmt.Errorf("Failed to send initial confirmation: %w", err)
Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +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
return err
Overhaul text messaging system to be like emails It's a better system for organization and makes it so we can have better logs about what gets sent.
2026-01-25 18:47:22 +00:00
}
Reference in a new issue Copy permalink