Uh oh!
There was an error while loading. Please reload this page.
Conversation
zbelzer
commented
Jul 27, 2012
Ah yes, it's already bound because it's an argument. I remember now. Thanks. |
Gurpartap
commented
Jul 29, 2012
Can you also add encoding to the gemspec, since there's a unicode only character in the author name 😄? That way I can point my Gemfile to your repo (without encoding issues, which cause an error otherwise). Update: This is apparently an issue with the parent repo itself. Sorry for posting here. |
Gurpartap
commented
Jul 29, 2012
There's an even sweeter way to utilize the proposed pull request: You'll need to add the following to the model though, too, to make the run_after_commit method accessible in state_machine block: |
wijet
commented
Jul 30, 2012
@tism Hey, could you please add this new block syntax to the README? Otherwise your pull request looks good. Thank you. @Gurpartap There is utf-8 encoding in the gemspec already. It seems to work, because when I remove it, I get encoding error. |
Gurpartap
commented
Jul 30, 2012
@wijet when I try I got around the problem with this in my Gemfile. But of course, I'm looking to not needing to specify that in the Gemfile. |
wijet
commented
Jul 30, 2012
@Gurpartap I cannot reproduce it, the way you shown it. Could you please paste the error? |
Gurpartap
commented
Jul 30, 2012
I guess it's those variables. Mine are not set to anything (intentionally). Can you try without those? (OS X, which most of us use, doesn't ship with those variables by default, afaik) |
Gurpartap
commented
Jul 30, 2012
Here's the error MRI ruby defaults to US-ASCII, iirc. |
wijet
commented
Jul 30, 2012
I've extracted this problem to #3 |
Modify run_after_commit to accept blocks
Patch to run_after_commit so it accepts blocks in place of a method