Closed aconfee closed 5 years ago
Hi
What is the content of your "sequelize-mock"? Could you provide a tiny example to illustrate it please?
Moreover, if I read well: we could see this:
Note: This is not an equivalent mock of Sequelize's built in QueryInterface at the moment. The built in object for Sequelize is undocumented and is marked as @private in their code, meaning it is not likely something to be relied on. If this changes it can be mocked here. Functions have been prefixed with the mock prefix ($) for this reason.
That means these methods are considerated as private and should not be called direclty.
Anyway, I could have a look to understand what after the mocking, these methods are not exposed
Many thanks
Regards
Close issue, due to no more feedbacks
Hello! I currently have the following, mostly default example, code which produces the error 'TypeError: MockDummyDao.$useHandler is not a function.'
Ultimately, all I'm trying to do is return a
null
, just null, not an object. This is what Sequelize actually returns when a record can't be found. This will then consistently test the following code in my service:Which behaves as expected live.
Any best way to return null, or insight into why $useHandler doesn't exist would be a huge help! Thanks!