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

Feature global/per-step configuration #380

Closed
josepjaume opened this issue Dec 19, 2016 · 0 comments
Closed

Feature global/per-step configuration #380

josepjaume opened this issue Dec 19, 2016 · 0 comments
Assignees

Comments

@josepjaume
Copy link
Contributor

🎩 User Story

In order to make features configurable depending on the step their process is in, we should expose global and per-step configuration.

Examples of global configuration of proposals:

  • Geolocalizable? [boolean]
  • Votable? [boolean]

Examples on per-step configuration of proposals:

  • Accepts new proposals [boolean]
  • Proposals can be voted? [boolean]
  • Voter [role]

The idea is to expand the feature's DSL in a way that integrating configurations is easy for the developer and is normalized across all features.

📋 Related documentation

None

🎯 Acceptance criteria

Features can expose global and per-step configuration and developers can easily access the current configuration to change the feature's behavior.

📌 Related issues

None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant