郑达里
That would probably be a bug somewhere in your application code. The tests for `fortune-http` work fine and don't emit warnings. Here's the server from the test: ```js const server...
Hmm, maybe you could try two things: - Use `http.createServer` directly just to see if the warning still occurs. - Wrap the arrow function with brackets to avoid returning the...
I can't reproduce the warning you're getting, throwing errors is working fine. Can you tell me which version you're using?
OK, I'll do a more thorough investigation then, the interesting part is `TypeError: Cannot read property 'payload' of undefined`.
I found the problem: the listener returns a promise that doesn't get a `catch`. The readme in `fortune-http` states: ```js const server = http.createServer((request, response) => listener(request, response) // Make...
If you want, you can call the `processResponse` method in the `fortune-json-api` serializer directly, you'd also have to mock a few things but it should be possible to do.
This should be in the other repo: https://github.com/fortunejs/fortune-http Have you looked at the tests? It is possible that the error message is correct and that you haven't added `require('fortune-json-api')` to...
+1
Oops, it seems the README is misleading, or at least only describes one direction. It is true that it camelizes field names from the request body when creating or updating...
This is expected, I think. Why are you trying to "filter" by ID? If you have the ID of a record, the URL always looks like this: ``` /:type/:id ```...