RexOps/Rex

Make features scope dependent

Open

#664 opened on May 3, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Perl (671 stars) (218 forks)batch import
help wantedready

Description

Currently all features and configuration options are global. So if someone activates a special feature in a module, this will be activated during the complete run and not only for functions that are in this module.

For example:

Module "A":

package A;
use Rex -feature => ['1.0'];

Rexfile:

use Rex -feature => ['0.57'];
use A;

Now the feature profile "1.0" is acticated and some functions the Rexfile author depends on might not work as expected anymore. This is why every module should use use Rex -base.

To prevent this and to allow module authors to load features only in their modules we need to make (at least) the feature flags scope dependent.

Contributor guide

Tech stack
None
Domain
backenddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
clear
Prerequisites
Perl programmingRex framework basicsUnderstanding of scope in PerlModule load order
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate how Rex currently loads features in the 'Rex' core module, specifically the import routine and feature activation mechanism. Look at the use of `use Rex feature => ['1.0']` in modules to understand how it sets global flags. Consider making feature activation lexical via 'our' but scoped to the calling package, perhaps using a per package hash. Since no PRs or comments exist, the exact implementation path is open.