Meteor-Community-Packages/meteor-user-status

Can we specify, which collection to write to?

Open

#92 opened on Mar 12, 2016

View on GitHub
 (0 comments) (2 reactions) (0 assignees)JavaScript (560 stars) (86 forks)batch import
enhancementgood first issue

Description

Instead of writing to the default Meteor.users collection can we configure it to write to a specified collection.

Contributor guide

Tech stack
javascript
Domain
backenddatabase
Issue type
feature
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
MeteorMongoDB collections
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the package source code, likely in the main module, to find where Meteor.users is referenced as the default collection. Look for existing configuration patterns (e.g., options object). Then propose adding a configurable collection name option, including fallback to current default. Since no comments or PRs exist, this is unexplored territory.