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

Add tests for migration code #30

Open
davidbanham opened this issue Apr 13, 2016 · 1 comment
Open

Add tests for migration code #30

davidbanham opened this issue Apr 13, 2016 · 1 comment

Comments

@davidbanham
Copy link
Contributor

No description provided.

@s-taylor
Copy link
Contributor

I was thinking about this and wondering if migrations should be a separate node module? I think any instances where a developer is unlikely to ever want to or need to change the code, it would be better separated. This also then reduces the clutter in redbeard when running generators and means as a developer you're not running migration tests every time you run your tests for code that you're never going to change.

Also rethinkdb-migrator might be a good open source candidate?

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