Priority settings missing?

[lukasza67]

Hello and thanks for a great work!

I have been going through the documentation and it seams that there is no way of setting the message priority for the notification. As it is now it sends with no settings and it gets "normal" priority by default at FCM-level. Or did I miss to set it manually somewhere?

I think this is a very important feature as on battery saving mode or locked screen the notification is now delayed until the user becomes active with the display.

[lukasza67]

So I've solved the issue by doing the following quick fix:

In the end of Push/Notification->getBody() I simply added:

$request['priority'] = "high";

Now; you might want to consider extend this within your management getters/settes to make this a real feature.

This made my notifications go in warp speed no matter of the devices state (I use cordova).

Also for housekeeping purposes 😃 the naming of function getBody() in this class is contradictory as it clashes with setBody(..) and it is not exactly the same type of "body" these two are playing around with (I managed to figure this out when I tried manually to build the full payload array body but the setter function just manages the message body).

My Regards to all for the nice work with the API once again!

[AndyGaskell]

Hi @lukasza67
That's really useful to know, thanks, I didn't realised normal priority push messages were treated that way. I'll have a look at writing a getter and setter for this.
Re getBody v setBody, I see what you mean, if we can't fix this in a non breaking way we can adjust the docs to better explain it.

[Philipp91]

Re getBody v setBody, I see what you mean, if we can't fix this in a non breaking way we can adjust the docs to better explain it.

How about renaming getBody() to buildJsonRequest() and leaving behind a deprecated getBody() that just redirects and will be removed in the next major release?

[Philipp91]

I'd also need the priority. I believe I could put together a PR if that helps.