Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make features scope dependent #664

Open
krimdomu opened this issue May 3, 2015 · 0 comments
Open

Make features scope dependent #664

krimdomu opened this issue May 3, 2015 · 0 comments
Labels
help wanted An idea where the project would need external help to realize ready An idea that is ready to be worked on

Comments

@krimdomu
Copy link
Contributor

krimdomu commented May 3, 2015

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.

@krimdomu krimdomu added this to the backlog milestone May 3, 2015
@krimdomu krimdomu changed the title Make features and configuration options scope dependent Make features options scope dependent May 8, 2015
@krimdomu krimdomu changed the title Make features options scope dependent Make features scope dependent May 8, 2015
@krimdomu krimdomu added the help wanted An idea where the project would need external help to realize label May 8, 2015
@ferki ferki added the ready An idea that is ready to be worked on label Mar 25, 2016
@ferki ferki removed this from the backlog milestone Mar 25, 2016
@ferki ferki added the Hacktoberfest A topic that is a good candidate for Hacktoberfest participants label Oct 11, 2016
@ferki ferki removed the Hacktoberfest A topic that is a good candidate for Hacktoberfest participants label Nov 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted An idea where the project would need external help to realize ready An idea that is ready to be worked on
Projects
None yet
Development

No branches or pull requests

2 participants