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

Decide between schema immutability and some locking concept #5

Closed
alexanderdean opened this issue Jun 20, 2014 · 1 comment
Closed
Assignees
Labels
Milestone

Comments

@alexanderdean
Copy link
Member

Basic idea: once a schema goes live it should be locked, so it can't be overwritten.

Or maybe we should just have a rule that schemas can never be overwritten. That would be cleaner.

@alexanderdean alexanderdean self-assigned this Jun 20, 2014
@alexanderdean
Copy link
Member Author

Decision with @BenFradet : allowing override goes against versioning. Let's make them immutable for now, we can always invent some kind of override behaviour later if required. Closing.

@alexanderdean alexanderdean added this to the Version 0.2.0 milestone Jul 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant