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

Warn about collision with reserved feature #30

Open
pcasaretto opened this issue Dec 19, 2016 · 1 comment
Open

Warn about collision with reserved feature #30

pcasaretto opened this issue Dec 19, 2016 · 1 comment

Comments

@pcasaretto
Copy link
Contributor

Naming a feature 'released_features' will cause problems for the user.
It is higly unlikely to happen, but worth a note in the README.

@matheusteixeira
Copy link
Contributor

I think that a better solution would be to change the value from released_features to a more unique one, like a hashed value, or add a "namespace", or something like that.

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

No branches or pull requests

2 participants