Rambaud Pierrick
Rambaud Pierrick
I'm setting the headers in the top navbar. 1. I would like to split the current documentation bewteen "getting started" and "advance usage". 1. In advance usage I would like...
> I also like the main page to be a short summary an image like you made in the previous PR: https://ipyvuetify--277.org.readthedocs.build/en/277/index.html. The main page in this PR is just...
my branch is again conflicting with main, @mariobuikhuizen, @maartenbreddels could you provide insight on what I should be doing to move forward? As you requested I'm making as small PR...
I think `filterContained` is clearly the best option, now the question is should it be a `ee.Filter` extension or a ImageCollection one ? I would vote for `ee.Filter` to make...
On my end I think you can drop the `filter` as it's already specified by the class and make it shorter. `contained` is sufficient to me but if you really...
I would prefer to code a filter first in a FilterAccessor and eventually wrap it in functions in `ImageCollection` and/or `featureCollection`. the same way `filterDate` is a wrapper around `ee.Filter.Date`.
I guess it is but the question is how Jupyter notebook itself prevent this behaviour ?
Is it also the case if you drop our theme and use the good old alabaster ? If it's the case then the issue is on myst-nb side.
I'm going to try your suggestion but as a side note I also tried another mechanism from my side: if you add: ```python # conf.py autoapi_ignore = ["*Html*", "*VuetifyTemplate*", "*generated*"]...
Ok so the skip event was the way to go. It's only disadvantage is that the files are read and build anyway, they are just not integrated to the toctree...