Serializable Meta allows the developer to specify, for a given model, a custom serialization model along with field mappings. This mechanism thus allows one model to act as another model when it comes to serialization.
The example herein shows how to manage different kinds of background jobs using https://github.com/qor/serializable_meta.
Define QorJob model and embed serializable_meta.SerializableMeta to apply the feature.
type QorJob struct {
gorm.Model
Name string
serializable_meta.SerializableMeta
}Add function GetSerializableArgumentResource to the model, so Serializable Meta can know the type of argument. Then define background jobs.
func (qorJob QorJob) GetSerializableArgumentResource() *admin.Resource {
return jobsArgumentsMap[qorJob.Kind]
}
var jobsArgumentsMap = map[string]*admin.Resource{
"newsletter": admin.NewResource(&sendNewsletterArgument{}),
"import_products": admin.NewResource(&importProductArgument{}),
}
type sendNewsletterArgument struct {
Subject string
Content string
}
type importProductArgument struct {}At first, Set a job's Name, Kind and SetSerializableArgumentValue. Then save it into database.
var qorJob QorJob
qorJob.Name = "sending newsletter"
qorJob.Kind = "newsletter"
qorJob.SetSerializableArgumentValue(&sendNewsletterArgument{
Subject: "subject",
Content: "content",
})
db.Create(&qorJob)This will marshal sendNewsletterArgument as a json, and save it into database by this SQL
INSERT INTO "qor_jobs" (kind, value) VALUES (`newsletter`, `{"Subject":"subject","Content":"content"}`);Now you can fetch the saved QorJob from the database. And get the serialized data from the record.
var result QorJob
db.First(&result, "name = ?", "sending newsletter")
var argument = result.GetSerializableArgument(result)
argument.(*sendNewsletterArgument).Subject // "subject"
argument.(*sendNewsletterArgument).Content // "content"Released under the MIT License.