We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looking at the mailboxer_notifications table is there any way to identify if a message is a reply?
What are the possible values for these fields as I only see them set to nil in the code.
"notification_code" "notified_object_type" "notified_object_id"
create_table "mailboxer_notifications", id: :serial, force: :cascade do |t| t.string "type" t.text "body" t.string "subject", default: "" t.string "sender_type" t.integer "sender_id" t.integer "conversation_id" t.boolean "draft", default: false t.string "notification_code" t.string "notified_object_type" t.integer "notified_object_id" t.string "attachment" t.datetime "updated_at", null: false t.datetime "created_at", null: false t.boolean "global", default: false t.datetime "expires" t.index ["conversation_id"], name: "index_mailboxer_notifications_on_conversation_id" t.index ["notified_object_id", "notified_object_type"], name: "index_mailboxer_notifications_on_notified_object_id_and_type" t.index ["notified_object_type", "notified_object_id"], name: "mailboxer_notifications_notified_object" t.index ["sender_id", "sender_type"], name: "index_mailboxer_notifications_on_sender_id_and_sender_type" t.index ["type"], name: "index_mailboxer_notifications_on_type" end
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Looking at the mailboxer_notifications table is there any way to identify if a message is a reply?
What are the possible values for these fields as I only see them set to nil in the code.
"notification_code"
"notified_object_type"
"notified_object_id"
The text was updated successfully, but these errors were encountered: