-
Notifications
You must be signed in to change notification settings - Fork 562
Open
Description
Describe the bug
There's a db hook feature that lets you create a hook that gets called only for a specific type of DbContext. The problem is that I've gone through the implementation and found no logic that would handle that. I created a dummy hook and bind it to a dummy db context and the hook is still called even when I use SmartDbContext.
To Reproduce
Steps to reproduce the behavior:
- Try creating a hook and bind it to any db context type but SmartDbContext.
- The result is that the hook will still be called even when SmartDbContext is used.
Expected behavior
The excepted behavior is the hook gets skipped unless the db context type in the db hook's metadata matches the current db context whose the SaveChanges() method has been called.
Screenshots
Desktop (please complete the following information):
It don't matter
Additional context
Reactions are currently unavailable