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.

Sign up for GitHub

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

Jump to bottom

Redo configuration entirely to better organize features #27

Open
zachbr opened this issue Jun 3, 2019 · 0 comments
Open

Redo configuration entirely to better organize features #27

zachbr opened this issue Jun 3, 2019 · 0 comments
Labels
priority: normal Issue has normal priority for resolution type: feature New feature or request
Milestone
2.0.0

Comments

@zachbr
Copy link
Owner

zachbr commented Jun 3, 2019

The current configuration format has some organizational issues. To fix them as extensively as I'd like, there will need to be some breaking changes made to its format.

Because this is not an API, we will treat this as "breaking" and will need to make this a 2.0.0 level change. Migration may be possible and considered.

Generally the purpose of this change is to allow much more extensive customization of features and how they apply to all sides of the bridge.
@zachbr zachbr added the priority: normal Issue has normal priority for resolution label Jun 3, 2019
@zachbr zachbr added this to the 2.0.0 milestone Jun 3, 2019
@zachbr zachbr added the type: feature New feature or request label Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: normal Issue has normal priority for resolution type: feature New feature or request
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@zachbr