firebase/functions-samples

Update fcm-notification sample to use latest API instead of legacy API

Open

#410 opened on May 25, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (3,957 forks)batch import
help wanted

Repository metrics

Stars
 (11,901 stars)
PR merge metrics
 (Avg merge 7d 23h) (5 merged PRs in 30d)

Description

How to reproduce these conditions

Sample name or URL where you found the bug fcm-notification

Failing Function code used (including require/import commands at the top) Update fcm-notification sample to use latest API instead of legacy API with reference to https://stackoverflow.com/questions/50505274/why-use-a-legacy-api-for-a-firebase-fcm-notifications-sample/50510755#50510755

Steps to set up and reproduce Line 74 of https://github.com/firebase/functions-samples/blob/master/fcm-notifications/functions/index.js

Contributor guide

Research direction
Study the Firebase Cloud Messaging HTTP v1 API documentation. Replace the legacy FCM API call in the fcm notification sample with the new HTTP v1 compatible call using Firebase Admin SDK. Ensure the sample code is consistent with the official Firebase documentation.
Tech stack
javascriptnodejs
Domain
backendapi
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptNode.jsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70