Niels Abildgaard

Hi @Rostyk, could you elaborate on what you mean with this issue? A link or a more elaborate description of the feature would be helpful :smile:

@Rostyk FCM is the new name for GCM. Unfortunately the name "FCM" is taken for npm libraries. This doesn't mean that we won't support FCM features, though, so let's look...

This would be a breaking change... maybe we should add a branch for breaking changes that will be merged into master at 1.0?

it would make sense if there was also a set function doing pretty much what we do now, but for any value: ``` js //Overwrite data field message.set("data", { knownValue:...

If `data` gets its own `addData` method, `notification` should have the same: ``` js message.addNotificationField("title", "Hello, World"); ```

I'm not quite sure I understand this correctly. If it is true that there is no new functionality added (that there is no functionality current unsupported by node-gcm), I agree:...

A source for this would indeed be good, so we can document this current deficiency. @jbruggeman do you have a subjective opinion on how much has changed between the API...

To be honest, a built-in way would be great :smile: if you feel like doing a PR on it, @davidvavra, we would definitely merge!

At the same time, we could probably remove lib/constants.js from the list of files that are exported. No outside part needs to see these. It clutters the interface.

The project has not yet been started, and this would require implementing a connection to an entirely new API. In addition, it would introduce concerns that we have not even...