Skip to content
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

feat: publish play-related CLI command #885

Merged

Conversation

FRSgit
Copy link
Contributor

@FRSgit FRSgit commented Sep 1, 2024

resolves #786

Description

Even though available in the repository README, the play-related CLI commands (play, playPublish, playVersionCheck, playRetain) are not publicly available in the CLI itself.

It turns out, that the code is there already - just needs to be uncommented. They all seem to be working.

I personally use the playPublish in my repository to fully automate publishing of my app to the Google Play (see the source here and here).

// case 'playRetain':
// return await play(parsedArgs as unknown as PlayArgs, 'retain');
case 'play':
return await play(parsedArgs as unknown as PlayArgs);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hi Jakub, did you test all 4 of these new commands? I doubt that the play command would work, because the play() function requires the second parameter command. I am not sure what the original author meant by this, but I suggest deleting the two lines above.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hey, you're right - I filed this PR rather lazily.
Check out new commit: I've move play commands into single namespace (so, all of the publish, retain, versionCheck commands are subcommands of bubblewrap play) and cleanup the implementation a bit - now it resembles other parts of the codebase more (mainly fingerprint/build commands).

I've also tested once again publish and versionCheck - they are working. Not sure about the retain - that's why I'm leaving it marked as "experimental" in the docs and in the implementation (there is an additional prompt, so the needs to confirm when they want to use an experimental feature).

What do you think?

cleanup play commands code
add play commands README
mark play retain command as experimental
Copy link
Collaborator

@OlegNitz OlegNitz left a comment

Choose a reason for hiding this comment

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

Thank you for putting more time into this change.

@OlegNitz OlegNitz merged commit df883b0 into GoogleChromeLabs:main Sep 9, 2024
1 of 4 checks passed
@FRSgit FRSgit deleted the feat/publish-play-related-cli-commands branch September 10, 2024 00:57
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.

ERROR "playPublish" is not a valid command!
2 participants