Skip to content

chore: remove api.json and use it from driver#288

Merged
yury-s merged 1 commit intomicrosoft:masterfrom
mxschmitt:enh/remove-api-json
Nov 12, 2020
Merged

chore: remove api.json and use it from driver#288
yury-s merged 1 commit intomicrosoft:masterfrom
mxschmitt:enh/remove-api-json

Conversation

@mxschmitt
Copy link
Copy Markdown
Contributor

Closes #278

@mxschmitt mxschmitt force-pushed the enh/remove-api-json branch from bd5d4fb to fb83059 Compare November 8, 2020 21:30
@mxschmitt mxschmitt requested a review from yury-s November 12, 2020 08:25
Copy link
Copy Markdown
Member

@yury-s yury-s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that api.json is not stored in the repo there is no way to tell what version of playwright was used to generated python APIs. Let's include playwright-cli version into *_apy.py when generating APIs?

@mxschmitt
Copy link
Copy Markdown
Contributor Author

Now that api.json is not stored in the repo there is no way to tell what version of playwright was used to generated python APIs. Let's include playwright-cli version into *_apy.py when generating APIs?

On the bots (GitHub Actions) we ensure that the generated script output is equal with the HEAD, so you can never make changes and forget to generate. By that we always know that the previous HEAD sync/async generated output was the generated with the version of the HEAD, in my mind its fine, or wdyt?

Copy link
Copy Markdown
Member

@yury-s yury-s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be good enough then.

@yury-s yury-s merged commit fe413f0 into microsoft:master Nov 12, 2020
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

Successfully merging this pull request may close these issues.

Remove api.json and use it from the driver as subprocess call

2 participants