inject-lazy implementation.

[tripodsgames]

First of all, I loved your project.
I would like to leave a contribution here for an alternative to asynchronous injection, it uses Proxies and intercepts access to the object.

HELP WANTED.

TODO

• Fix Maximum call stack size exceeded.
• Improve Tests.
• Create docs about the feature.

[zheksoon]

Wow, that's huge!!!

Thanks a lot for the contribution, I will merge it in a separate branch and add some refactoring (already have it done)

[zheksoon]

Ok, so the main changes of the refactoring:

• Now you don't have to wrap the class you are injecting into arrow function. You can just use usual class name, like this:

  constructor(public instanceB = injectLazy(CircularDependencyB)) {}

  If you see a usecase for the arrow function, let me know - it should be easy to add

• New error has been added, now it's just generic, with a lengthy text:
  Transient scope for class ${cls.name} was resolved too many times in one tick. This is likely an infinite loop.
  It signifies that you have resolved one class too many times during one microtask, so this means you are likely in an infinite loop (he-he, the same words)

Otherwise, that's great contribution, and I'm happy to see the real people use it!

[tripodsgames]

Thanks for the feedback and the changes.

Some comments I forgot to add:

• One of the things I had to change in the tests was toBe for toEqual, as the Proxy cannot intercept ===.
• The arrow function is not really necessary.
• Performance using proxies is lower, but this helps in places where we cannot modify the logic to add injectAsync.(That's my case)

[zheksoon]

@tripodsgames Hi! Could you please elaborate a bit more about your specific usecase to understand what's (maybe) missing in the implementation, or make it in a different way (for example, loop detection). Appreciate any help :) Thanks!

[tripodsgames]

@zheksoon Unfortunately I'm out of time lately, but I'll collect the information and update the documentation

[zheksoon]

@tripodsgames maybe just continue in the thread, I think we could come to better decisions together :)

What I don't like in the current implementation (the inject-lazy branch) is loop detection. It's a bit rough to detect cycles by limiting the number of transient resolutions, so need to think a bit more about it

[tripodsgames]

@tripodsgames maybe just continue in the thread, I think we could come to better decisions together :)

What I don't like in the current implementation (the inject-lazy branch) is loop detection. It's a bit rough to detect cycles by limiting the number of transient resolutions, so need to think a bit more about it

I'm studying a way to eliminate the problem of cycles, I know it's possible