Skip to content

Docs about new *byRole capabilities (+ Blog post?) #283

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
afontcu opened this issue Jun 11, 2019 · 3 comments
Closed

Docs about new *byRole capabilities (+ Blog post?) #283

afontcu opened this issue Jun 11, 2019 · 3 comments

Comments

@afontcu
Copy link
Member

afontcu commented Jun 11, 2019

Hi! I guess the addition of #280 should be documented.

I'm up for it, just wanted to clarify some doubts:

  • Did the "level of recommendation" for *byRole change? (source). I feel these queries got way more powerful now.

  • Would a blog post be useful, too? Bot this and package scoping are quite big changes IMHO.

Actually, when writing these lines, I thought of something else. Right now, React/Vue/etc Testing Library users benefit from DTL additions, but they need to check DTL changelog to be aware of that. So, how would you feel about having like a "global" changelog for all the Testing Library ecosystem?

@kentcdodds
Copy link
Member

I love all of the ideas 👍

@alexkrolick
Copy link
Collaborator

alexkrolick commented Jun 11, 2019

The changelogs are autogenerated, but a blog post on the docs would be great.

Definitely need one for the package scoping change.

@afontcu
Copy link
Member Author

afontcu commented Jun 12, 2019

Thanks both for the input!

@alexkrolick "changelog" is probably not the best way to put it. I think what I was trying to solve is that right now people need to look at several places to know about the news (DTL docs, VTL/RTL/etc docs, and so on).

Anyway, I'm closing this issue (I just noticed I opened it in the wrong repo 😂 damn) and opening a PR for blogpost, and another issue once I came up with a better suggestion for "unified" docs :)

Again, thanks!

@afontcu afontcu closed this as completed Jun 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants