Ernesto García

@diegohaz do you mean that this library could provide both custom matchers, right?

This issue is about ``. Can you open an issue about progress bars?

The `toHaveDisplayValue` custom matcher has the following purpose: > This allows you to check whether the given form element has the specified displayed value. A progress bar, or a `role="slider"`...

Is this issue relevant, considering how outdated Node v14 is? Though we still seem to support it, but I'd rather fix this by dropping support for Node v14. Thoughts?

I think it could be of use to have a `toHaveRole` custom matcher, because it is not as straightforward as simply checking it with `.toHaveAttribute('role', 'button')`. Native buttons won't have...

The problem with… ```js expect(editHandle).toHaveProperty('tagName', 'BUTTON'); ``` …is that such a test will break if for some reason a `` is changed for something with `role="button"`. Albeit uncommon, there could...

I have no big objections to this. One potential problem with this is `flex-direction: row-reverse`, `flex-direction: column-reverse` and some configurations of `display: grid` where the visual order is not the...

I'm glad that this has fixed the issue for some. Unfortunately, it seems to be a source of problem for others. See https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/65987#discussioncomment-6371630 And we already have a pull request...

Something introduced in this PR has broken the tsdx build command. I noticed first on CI, but when I run it locally I can reproduce. To do so, run this...

I have this issue as well. When using the epic-stack. For some reason, it does not happen normally, but it happens when I attempted to dockerize the app locally for...