-
Notifications
You must be signed in to change notification settings - Fork 35
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
Content-type parsing #47
Conversation
skol-pro
commented
Mar 17, 2016
- Created Content-Type module + factory
- Refactored resource-http-interceptor factory to use content-type checker
- Refactored resource-http-interceptor factory to use content-type checker
Could you add the bower & npm dependency? |
See my comment on #46 |
Ah, sorry.
npm install content-type --save
bower install --save jshttp/content-type
npm install
npm run compile
|
Awesome ok, I already ran npm install but I was afraid that it would create useless stuff. Thank you for the test, will take a look then. |
The |
Ooooh ok I see. |
Ok I added dependencies etc. No need for new pull-request ? |
If you push again, the pull request will get updated. |
Ok, already pushed, good. |
This is the test I wrote: I had to improve a few things which you see in the latest commit. Thank you very much. |
Cool, all of this makes sense ! |
When angular creates a service, it does it using 'new service()' which will create an instance. |
BTW: I just made an improvement to the README. |
Oh really, thought returning |
function withReturn() { return this;}
function without() {}
withReturn() // withReturn {}
new withReturn() // withReturn {}
without() // undefined
new without() // without {} |
Ah ah :D Ok ok, not sure I got that but that's ok, will keep in mind too. |
You should had the content-type dependency in the README too. |
I mean, for those like who haven't installed angular-hal using npm at least. |
I opened an issue. I'll do it tomorrow. |
Hehe, have a good-night ;-) |