Meteor-Community-Packages/meteor-roles

Handle large role collection by persisting on client when user is logged it.

Open

#332 opened on Feb 27, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (919 stars) (161 forks)batch import
enhancementhelp wanted

Description

I have a very complex and large role collection. Since these permissions are needed when the user is logged in, it takes quite some time for my application to load. I have more than 300 inherited roles and this may actually grow larger. Is there a way to persist roles on the client and only read from the client as long as the user is logged in? This package actually helps in persisting the roles on the client. But how can I connect the role package to this persisted collection on the client?

Contributor guide

Tech stack
javascriptmongodb
Domain
performanceauthorization
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-2 days
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
Meteor basicsMinimongo knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how the roles package currently stores role data on the client (likely in a Minimongo collection). Examine the persistant minimongo2 package to understand its API for persisting collections. Modify the roles package to optionally use a persistent collection for roles when a user is logged in, potentially by overriding the default collection or adding a setting. Check the roles package source code (e.g., client side files) for the collection definition and update logic.