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
Updates for latest version of Journey #16
Conversation
Could you help clarify a few points? I'm ready to update to the new Journey APIs, but it seems all the tests for webservice.js are still passing here when using Journey 0.4.0-pre-2. Are you seeing the same behavior? I might be messing up here. Either way, I'm thinking we might need to add a few more tests if you were seeing failures but the tests were reporting all passing, I'd like to keep the coverage for this library high. |
Ohh, and thank you for the patch! :-) |
I didn't run the tests, I only tried to create a simple webservice using the library. Among other things it triggered this error from Journey:
The changes in this pull request are only what I needed to get the basic functionality running at all. The Journey version I used was also 0.4.0-pre-2. After this pull request I spent another hour bugfixing, eventually gave up and wrote my own webservice generator. I honestly don't know if I was doing something totally wrong (probably). :) |
Well, best of luck with that! In the future, you should probably pay attention to which versions you are using and what tests are passing. Current package.json specificies the Journey version @ 0.2.8 So I'm sorry you wasted your time trying to use the wrong version and not running any of the tests. |
Relax, I'm not trying to diminish your work or anything. If Journey breaks downward compatibility in their library that's their problem not yours. I still really like webservice.js and am using it in several other projects, it's just not right for this particular one. (The journey 0.4.0 requirement isn't the only reason, the client also wanted a domain-specific language for the modules rather than plain CommonJS modules.) Regarding the package.json, it currently specifies 0.4.0-pre-2 (because of the ">="). To have npm use 0.2.8 instead, specify "= 0.2.8" or a range like ">= 0.2.8 < 0.4.0". I ran the tests against both master and my branch:
So current master crashes (for me) and my branch fails two tests. I'll take a look if I can fix the remaining two. Sorry for not running the tests before submitting the pull request. |
The test suite now runs cleanly:
Unfortunately github didn't update the pull request with the new commit - perhaps because it was closed when I committed it? In any case here it is, it's a one-liner: |
I'm totally retarded. I was operating in the 0.5.0 branch, not master. I totally forgot I had fixed all this already in https://github.com/Marak/webservice.js/commits/v0.5.0 Sorry for the confusion, I'm merging everything into master now. |
The journey library apparently mixed up its API quite a bit since the last release of webservice.js. This pull request contains the changes I needed to get it to work.