Skip to content
This repository was archived by the owner on Jan 6, 2018. It is now read-only.
This repository was archived by the owner on Jan 6, 2018. It is now read-only.

add support for different notification keys #10

@omid-khd

Description

@omid-khd

currently all notifications to gcm servers are sending with 'data' key. for those who don't want to use this method handeling 'data' key is confusing. that is, if you don't provide value for $data variable in the send method json encoded string that will be send to the gcm servers is somthing like:

{
    "notification" : {
        "title" : "title of notification",
        "body" : "content of notification"
    },
    "data": null,
    "registration_ids" : [
        "registration_ids goes here"
    ]
}

or:

{
    "notification" : {
        "title" : "title of notification",
        "body" : "content of notification"
    },
    "data": [],
    "registration_ids" : [
        "registration_ids goes here"
    ]
}

or

{
    "notification" : {
        "title" : "title of notification",
        "body" : "content of notification"
    },
    "data": {},
    "registration_ids" : [
        "registration_ids goes here"
    ]
}

and i don't know if this values are acceptable with gcm.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions