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

Implement embed_migration! using macros 1.1 #470

Closed
wants to merge 1 commit into from

Conversation

weiznich
Copy link
Member

@weiznich weiznich commented Oct 9, 2016

  • port embed_migration to macros 1.1
  • remove codegen_old
  • some minor fixes

This is a breaking change, because the root path passed to embed_migrations! have changed. It's now CARGO_MANIFEST_HOME, but was before the location of the file that called that macro.

@weiznich
Copy link
Member Author

weiznich commented Oct 9, 2016

Travis is failing while building compilertest. Any idea why?

@killercup
Copy link
Member

Sorry, I haven't had time to look at this so far :(

The CI error is because this compiles compiletest 0.2.4 which expects a nightly from 2026-10-07 (see Manishearth/compiletest-rs#50; we use 2016-09-29). You probably need to change the dependency to =0.2.3.

@weiznich
Copy link
Member Author

Using compiletest 0.2.3 didn't fix this.

@@ -6,4 +6,4 @@ authors = ["Sean Griffin <sean@seantheprogrammer.com>"]
[dependencies]
diesel = { version = "0.7.1", features = ["sqlite", "postgres"] }
diesel_codegen = { version = "0.7.2" }
compiletest_rs = "0.2.1"
compiletest_rs = "0.2.3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to write compiletest_rs = "=0.2.3" with the = before the version number or Cargo will treat this as ^0.2.3.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, didn't know about this one.

* port embed_migration to macros 1.1
* remove codegen_old
* some minor fixes
@sgrif
Copy link
Member

sgrif commented Oct 10, 2016

Can you submit the API change as a separate PR without re-implementing it? That will make it much easier to review.

@sgrif
Copy link
Member

sgrif commented Oct 10, 2016

I'm wanting to release today, so in order to make sure things move quickly I'm going to go ahead and take over here and make the changes I'd like to see (and split up the PR into smaller commits). I'll make sure you're credited on the commits that go in.

@sgrif
Copy link
Member

sgrif commented Oct 10, 2016

Relevant code pulled into #471 and #472.

@sgrif sgrif closed this Oct 10, 2016
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

Successfully merging this pull request may close these issues.

3 participants