PipedreamHQ/pipedream

[TRIGGER] Changes to a Mongo Atlas Collection

Open

#255 opened on Jul 16, 2020

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)JavaScript (5,305 forks)batch import
blockedenhancementgood first issuehelp wantedtrigger / source

Repository metrics

Stars
 (7,438 stars)
PR merge metrics
 (Avg merge 9d 7h) (131 merged PRs in 30d)

Description

See the Mongo Atlas trigger docs for more information.

Contributor guide

Research direction
Review the MongoDB Atlas trigger documentation and understand how to implement a change stream trigger in a Pipedream component.
Tech stack
javascriptnodejsmongodb
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Mostly clear
Prerequisites
JavaScriptMongoDBPipedream components
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60