Xarray flexible indexes blog post #597
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@benbovy is attempting to deploy a commit to the xarray Team on Vercel. A member of the Team first needs to authorize it. |
for more information, see https://pre-commit.ci
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Long overdue, but still very much work in progress!
I've just added the outline, where I'd like to show what the index refactor addresses and/or enables from the basic to the most advanced use cases. The goal is also to refer to this blog post when commenting on new Xarray issues related to this topic.
Once it is ready, probably best would be to wait for an Xarray stable release before publishing it (ideally with the documentation further improved).