Tim Deschryver

First, I like the idea. My initial thought is that the developer needs to first suspect that there's an issue, and that it's caused by a selector. What if we...

@MikeRyanDev to be honest, haven't thought that far 😅 I think you're right that it would be hard (impossible?) to retrieve the name of the selector. The closest we can...

I might be wrong but I think `networkError` can't be used with `once` currently. As a work around you might want to use the status to create a falsy response...

Have you tried running this with [msw v.0.30](https://github.com/mswjs/msw/releases/tag/v0.30.0) ? This includes a fix for Jest 27.

Because ATL invokes an Angular detection cycle within the `waitFor` callback, we might end up in an infinite loop because this leads to a mutation of the DOM in some...

Another possibility would be to send the trigger (interval timer or observer) to the callback. This way consumers could use the trigger to branch off their logic. For ATL specific,...

Hi, AFAIK this is intended. The `exact` is a configuration for the role name, not for the `name` config. You can see this behavior in [a test](https://github.com/testing-library/dom-testing-library/blob/main/src/__tests__/element-queries.js#L783).

A RegExp is already supported. https://testing-playground.com/gist/310d8a2431e7eabe8efc81babf14222b/0299a286fbc844f140e64a31c2670055983b1307 I think what @JesusTheHun is asking, is that `MatcherOptions` can also be used for the name (which is currently a string, RegExp, or function)

@johachi findBy wait a few moments (I don't know the default) before it throws, which slows down the test. Have you tried using `getBy`? ``` await waitForElementToBeRemoved(() => screen.queryByRole("status")); ```

To be good we should change the [compilation mode](https://angular.io/guide/angular-compiler-options#compilationmode) to 'partial'. If you want, you can create a PR for this.