Sergii Stotskyi

Probably no, but I think that I will fix it till the end of this year. Just not a priority for me right now, sorry guys

No any updates guys, sorry guys.

it seems that [jest-circus](https://github.com/facebook/jest/blob/main/packages/jest-circus/src/state.ts#L44) exports access to its state, which potentially means I can add integration for it without changing the public interface.

However, I still think that bdd-lazy-var need to go in the direction of being more independent from testing framework integration and being more typesafe with less hacks. This is what...

This is interesting. I see only one issue. this library allows to use lazy variables in `beforeAll` and `afterAll` hooks. But for this specific helper, I can actually say that...

However, I plan to rewrite library API to something [like this](https://github.com/stalniy/bdd-lazy-var/issues/97#issuecomment-774303775). This will allow to greatly simplify integration with testing frameworks. But not sure when this happens. Don't have enough...

Thanks for the issue. Indeed, bdd-lazy-var wraps `describe` statements in order to track suites. I’ll try to add a bit smarter to logic for features like this one.

@nzacca Unfortunately, it's not so simple. If you do like this, you will have `describe.each` and `test.each` but bdd-lazy-var won't be able to track dynamically created `describe` statements in `describe.each`...

It’s quite hard to add types for that functions because their types depend on chosen testing library (mocha/chai, jasmine or jest)

Hi there. Thank you for the proposal. Looks like docs for cookbook section. Example with prisma is ok. You can then add it to https://github.com/stalniy/casl-examples I’d suggest to implement blog...