ale04/14/2022, 5:35 PM
Anna Geller04/14/2022, 5:37 PM
ale04/14/2022, 5:38 PM
collection on my local environment 😊 Here you can find the code! What are the next steps to submit the code into Prefect repo?
Anna Geller04/18/2022, 10:48 AM
alex04/18/2022, 1:30 PM
. We recommend at least 80% coverage. • Make sure that all the documentation is updated. This includes the docstrings in your Python code and README.md since they are used to generate your documentation. You can run
coverage run --branch -m pytest tests
to view the generated documentation. • Publish a version of
on PyPI. You can do this automatically by creating a tag in GitHub with a v prefix (e.g. v0.1.0). This will create a release on PyPI and also publish the autogenerated docs to GitHub Pages. You’ll need a PyPI to to publish to PyPI and you can refer to MAINTAINERS.md in your repo for more information. Once you’ve completed the initial release, we can work together to get
listed in the Prefect Collections Catalog. If you run into any issues, let me know and I’ll be happy to help!
ale04/20/2022, 3:26 PM
on PyPi 🎉 https://pypi.org/project/prefect-cubejs/
alex04/20/2022, 3:36 PM
ale04/20/2022, 3:39 PM
alex04/20/2022, 3:48 PM
ale04/20/2022, 3:49 PM
alex04/20/2022, 4:20 PM
need to be filled in. Can you you add a docstring that documents the arguments, return type, and examples for the task similar to these tasks here: https://github.com/PrefectHQ/prefect-slack/blob/main/prefect_slack/messages.py?
ale04/20/2022, 4:44 PM
alex04/20/2022, 7:06 PM
in the new docstring, but I think that should be
ale04/20/2022, 7:07 PM
alex04/21/2022, 6:22 PM
) since mkdocs can pull typing info from the type hints on your function. If you want to experiment with changes to the documentation on your local you can run
which will rebuild the docs each time you make a change.
ale04/21/2022, 8:13 PM
alex04/22/2022, 4:25 PM