Augustin Le Fèvre

@n1ru4l I updated the tests to only cover deprecated arguments :)

Seems good to me, what I'm working on (even if it's paused right now) don't use the mutations^^ But yes, since there won't be any conflicts, I'm good with that.

Overall I'm all for always returning the same type of component. From a user-land perspective, what is the difference between a host and composite component (apart from `node.type`)? What types...

Thanks a lot for the detailed explanation, helps a lot! Definitely something we should add to the doc when doing this change. I think it would be good, but we...

> The change could be very confusing though and quite hard to debug so a migration guide with a detailed explanation of the change and its involvements would probably be...

There is a valid point of if RN should support more roles. However, if you look at RTL, they do support by themselves both the raw dom element and custom...

I think we could take some inspiration from [aria role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles), which is more exhaustive than `AccessibilityRole` (that I feel designed as something to set, rather than to query). If we...

I'm pretty sure it's the same as #1093. If you use react 18, we seem to have issues with some cases. In the linked issue there is an attached PR...

> I am especially curious whether byRole is ready to be promoted as primary query, or should we implement implicit roles for RN views first as mentioned in https://github.com/callstack/react-native-testing-library/issues/1130. We...

Created the corresponding issue #1134. We might even consider marking `ByA11yState` queries as deprecated once the accessibility state support has been added to `ByRole`.