-
Notifications
You must be signed in to change notification settings - Fork 23
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
Generate client modules from spec? #5
Comments
Hi @michallepicki, Thanks for reaching out... great question/suggestion. We'd been holding off on code generation while learning how to go about this, but do like the idea and it feels like it's now probably about time to implement. We'll take a look at that example and see what we can do to get started. Also, happy to take PRs :) |
I was looking at this task and, not wanting to discourage you, gave up when I was doing my internal experiment with playwright and elixir. The major problem for me was that the API Playwright exposes is really Object Oriented in nature, making the translation not as natural as it is in Ruby, JavaScript or C#. Really curious what you come up here :) |
That's a good point, @hubertlepicki, and something I've struggled with from time to time: when to make things look more like Playwright vs. when to make them more like Elixir. So, I think that, for now, we'll probably continue with manual additions/fixes until getting close to feature parity. Then we can use the insights gained to see what sorts of automated generation would make best sense. |
Hi!
I saw that other similar projects (playwright-sharp and others) generate the client modules from playwright API specification JSON file.
Is there plan to do the same here? There are multiple ways to do that in Elixir I think, one could be an approach similar to what chrome_remote_interface Elixir package does.
The text was updated successfully, but these errors were encountered: