Open paul-marechal opened 1 year ago
Maybe a different issue but I had this problem while dealing with this error: What's the recommended way to troubleshoot which binding is causing the sync resolution to fail? I ended up editing Inversify's sources in my node modules to print what service identifier caused resolvedRequests.isAsync
to become true
but that feels like a workaround.
Expected Behavior
I don't expect the LAZY_IN_SYNC error to fail when displaying symbols.
Current Behavior
LAZY_IN_SYNC fails to display symbols.
Possible Solution
Call
.toString()
explicitly before printing the symbol.Steps to Reproduce (for bugs)
Context
We recently migrated to Inversify 6 and had to deal with this error.
Your Environment