db-migrate/node-db-migrate

Add excludeFromAll setting to scope config

Open

#509 opened on Nov 1, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (2,296 stars) (367 forks)batch import
featuregood first issuehelp wanted

Description

Description

Add an excludeFromAll setting to the scope configuration, which will help when scopes exists that are only targeted at development.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Tech stack
javascriptnodejssql
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of node db migrateunderstanding of scope configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Start by examining the scope configuration in `lib/scope.js` to understand how scopes are currently defined and used. Look for the place where scope settings are parsed and applied during migrations. Implement a new boolean property `excludeFromAll` on scope objects, and modify the migration runner to skip scopes with this property when executing 'all' scopes. Add unit tests covering the new behavior. Check existing tests for scope related features as templates.