Skip to content

Commit 7e11188

Browse files
authored
DOC: Options A and A -> Options A and B (#11127)
* DOC: Options A and A -> Options A and B * DOC: Revise the wording to "Options 1A and 2A"
1 parent ac3b80c commit 7e11188

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

design_notes/flexible_indexes_notes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -150,15 +150,15 @@ In general explicit index creation should be preferred over implicit index creat
150150

151151
For which coordinates?
152152

153-
- A. only 1D coordinates with a name matching their dimension name
154-
- B. all 1D coordinates
153+
- 1A. only 1D coordinates with a name matching their dimension name
154+
- 1B. all 1D coordinates
155155

156156
When to create it?
157157

158-
- A. each time when a new Dataset/DataArray is created
159-
- B. only when we need it (i.e., when calling `.sel()` or `indexes`)
158+
- 2A. each time when a new Dataset/DataArray is created
159+
- 2B. only when we need it (i.e., when calling `.sel()` or `indexes`)
160160

161-
Options A and A are what Xarray currently does and may be the best choice considering that indexes could possibly be invalidated by coordinate mutation.
161+
Options 1A and 2A are what Xarray currently does and may be the best choice considering that indexes could possibly be invalidated by coordinate mutation.
162162

163163
Besides `pandas.Index`, other indexes currently supported in Xarray like `CFTimeIndex` could be built depending on the coordinate data type.
164164

0 commit comments

Comments
 (0)