Closed ChuWeiChang closed 1 month ago
After this PR is merged, don't publish the project by hand since I will setup GitHub Actions to automate this. If you're willing to try and learn setting up GitHub actions, please let me know.
After this PR is merged, don't publish the project by hand since I will setup GitHub Actions to automate this. If you're willing to try and learn setting up GitHub actions, please let me know.
You can leave this to me.
Because the
**kwargs
wasn't supported inBlock.handle()
, please update the usage example.
Can you be more specific on this? Since we currently use json array, so handle is called by Block.handle(*arg). I don't quite follow.
After this PR is merged, don't publish the project by hand since I will setup GitHub Actions to automate this. If you're willing to try and learn setting up GitHub actions, please let me know.
You can leave this to me.
@ChuWeiChang
Here is the docs for GitHub Actions: https://docs.github.com/en/actions
You can create a new workflow file which is triggered by release published. Whenever the release is published, the workflow will test the code first, and if no error, just publish it to PyPI.
Create a separate issue and PR to handle GitHub Actions.
Because the
**kwargs
wasn't supported inBlock.handle()
, please update the usage example.Can you be more specific on this? Since we currently use json array, so handle is called by Block.handle(*arg). I don't quite follow.
Since most programming languages don't support keyword arguments, we use JSON array to describe arguments list. Because of that, *args
should be used instead of **kwargs
Since most programming languages don't support keyword arguments, we use JSON array to describe arguments list. Because of that,
*args
should be used instead of**kwargs
Didn't know you were mentioning README.md. It's updated now. As for the github actions, I will ask for re-review after they are set up
Since most programming languages don't support keyword arguments, we use JSON array to describe arguments list. Because of that,
*args
should be used instead of**kwargs
Didn't know you were mentioning README.md. It's updated now. As for the github actions, I will ask for re-review after they are set up
You can send review request and I'll check the publish details. For GitHub Actions, create a new issue and PR.
4 #8
I just published the library onto pypitest. The email part currently leads to mine, since I lost track of our collective email account on Cloudflare. This is just a publishing test, and official publish will be made after the email section is set correctly and this PR is approved.