docs: restore assets in the documentation #355
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #353
It's a way bigger PR than expected. The disparition of the Asset object from the documentation made me realise that I made a huge mistake when building the files. having a file with the same name as it's unique class (Asset.py, Asset) is crashing the autopai builder becaue it creates a duplicate at the same level in
path.sys
. This would be irrelevant if we were not dealing with a extention API but as none of our methods are directly called it creates an implicit circular imports of "Asset".I thus renamed the Asset file into "ee_asset". For consistency I renamed all the other files to
ee_<object in snake case>.py
. IT IS NOT CHANGING ANYTHING FROM A USER POV.Also this forced me to revisit the docstring Sphinx roles that is now fully independant from
:py:meth:
.