feathers-mongoose and v5 #3115
Replies: 2 comments
-
Additional info...my failing tests are related to prototype definition mismatch, perhaps due FeathersError being a function constructor in v4 but implemented as class in v5? for example, a users service backed by feathers-mongoose model: await assert.rejects(
app.service("users").create({
username: faker.internet.userName(),
email: "xyz"
}),
BadRequest
)
|
Beta Was this translation helpful? Give feedback.
-
@daffl could you provide any feedback/guidance here? Is the expectation that feathers-mongoose will be refactored to support v5? my upgrade is on hold until i can get a better understanding of how to proceed. |
Beta Was this translation helpful? Give feedback.
-
HI,
My project relies heavily on feathers-mongoose, which is currently pinned to v4. I have some failing tests after migrating to v5, of which I think are due to some changes coming from feathers/[email protected] can post a repro if needed, but wanted to get this raised first.
There is currently an open failing merge PR for v5.
Is feathers-mongoose@5 on the horizon?
Beta Was this translation helpful? Give feedback.
All reactions