db-migrate/node-db-migrate

Add executeAfter setting to scope configuration

Open

#511 opened on Nov 1, 2017

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

Description

Description

Add an executeAfter setting to the scope configuration, to prepare the ability to modify the order of execution when executing groups or via the all statement.

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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with node db migrate scope configurationBasic understanding of execution order
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the current scope configuration implementation in the node db migrate codebase, likely in files like 'lib/scope.js' or similar. Understand how groups and 'all' statements execute. Add an 'executeAfter' property to the scope configuration object, ensuring it integrates with existing execution logic. Review any related tests to ensure compatibility.