-
Notifications
You must be signed in to change notification settings - Fork 149
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
Simple selector engine #1
Comments
I'll assume this issue is about the part of API surface of From what I understand, we want to provide both:
I think that we should implement the basic functionality first and then figure how to create whole flows out of them. We have to encode native finders into a JSON, send it to the instrumentation server, and then recreate it somehow into calls to native |
Kind of done for now. The paragraph and code snippet about native selectors might be useful in the future. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
No description provided.
The text was updated successfully, but these errors were encountered: