RexOps/Rex

Make features scope dependent

Open

#664 建立於 2015年5月3日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Perl (671 star) (218 fork)batch import
help wantedready

描述

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.

貢獻者指南

技術棧
無
領域
backenddeveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Perl programmingRex framework basicsUnderstanding of scope in PerlModule load order
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
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.