Deprecate Particle.publish() and Particle.subscribe() invoked with default event scope

[sergeuz]

Problem

Beginning with 0.8.0 release, Particle.publish() and Particle.subscribe() methods will require event scope to be specified explicitly. This change will potentially break a lot of existing applications.

Solution

Generate deprecation warning when Particle.publish() and Particle.subscribe() are used with a default event scope.

Steps to Test

Compile and run wiring/api test.

Example App

void setup() {
    // Particle.publish()

    Particle.publish("event");
    Particle.publish("event", "data");
    Particle.publish("event", "data", 60);

    // Particle.subscribe()

    void (*handler1)(const char*, const char*) = nullptr;
    Particle.subscribe("event", handler1);

    std::function<void(const char*, const char*)> handler2;
    Particle.subscribe("event", handler2);

    struct Handler3 {
        void handler(const char*, const char*) {
        }
    } handler3;
    Particle.subscribe("event", &Handler3::handler, &handler3);
}

void loop() {
}

---

Completeness

• User is totes amazing for contributing!
• Contributor has signed CLA (Info here)
• Problem and Solution clearly stated
• Run unit/integration/application tests on device
• Added documentation (N/A)
• Added to CHANGELOG.md after merging (add links to docs and issues)

---

Deprecated API

[PR #1365] Beginning with 0.8.0 release, Particle.publish() and Particle.subscribe() methods will require event scope to be specified explicitly. Please update your apps now to include the event scope to avoid compilation errors in >=0.8.0