You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2023. It is now read-only.
I might be wrong, but it's so weird that the npm package v2.8.0 is not the same with the latest repo on github. After npm i -S feathers-mongodb, the \lib\index.js#279 is:
returnPromise.reject('Not replacing multiple records. Did you mean `patch`?');
but the same line in the repo forked from github's master branch (after compliation with npm test) is:
returnPromise.reject(new_feathersErrors2.default.BadRequest('Not replacing multiple records. Did you mean `patch`?'));
The later one is OK, but the first one generates wrong format of error.
Expected behavior
Tell us what should happen
Actual behavior
Tell us what happens instead
System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
2.8.0 NodeJS version:
7.10.0 Operating System:
windows 10 with linux sub system Browser Version:
React Native Version:
Module Loader:
The text was updated successfully, but these errors were encountered:
Steps to reproduce
I might be wrong, but it's so weird that the npm package v2.8.0 is not the same with the latest repo on github. After
npm i -S feathers-mongodb
, the\lib\index.js#279
is:but the same line in the repo forked from github's master branch (after compliation with
npm test
) is:The later one is OK, but the first one generates wrong format of error.
Expected behavior
Tell us what should happen
Actual behavior
Tell us what happens instead
System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
2.8.0
NodeJS version:
7.10.0
Operating System:
windows 10 with linux sub system
Browser Version:
React Native Version:
Module Loader:
The text was updated successfully, but these errors were encountered: