issue_comments
7 rows where issue = 1306887842 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- display the indexes in the string reprs · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1276433539 | https://github.com/pydata/xarray/pull/6795#issuecomment-1276433539 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85MFNSD | benbovy 4160723 | 2022-10-12T16:19:34Z | 2022-10-12T16:19:34Z | MEMBER | Looks good to me @keewis. Thanks for your work on the indexes repr! Yes I think we can skip displaying default indexes for now... The question is which indexes are considered as default, i.e., all
Yes that's a good point. Let's keep "dimensions without coordinates". |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 | |
1266702407 | https://github.com/pydata/xarray/pull/6795#issuecomment-1266702407 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85LgFhH | keewis 14808389 | 2022-10-04T09:59:29Z | 2022-10-04T15:28:25Z | MEMBER | not really, I wanted to wait until Edit: we don't yet have tests, though There's two issues left that might need a bit of discussion: in 8f21df3 I skipped displaying default Another proposal we had was to replace the "dimensions without coordinates" line with a "coordinates without index" line. @benbovy, this might be a misunderstanding on my part, but I thought "dimension coordinates" (and in particular their indexes) are still used for alignment? If so, I think we might need both lines. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 | |
1266033247 | https://github.com/pydata/xarray/pull/6795#issuecomment-1266033247 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85LdiJf | dcherian 2448579 | 2022-10-03T20:52:24Z | 2022-10-03T20:52:24Z | MEMBER | I think we should move forward here. Are there any real blockers? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 | |
1248532873 | https://github.com/pydata/xarray/pull/6795#issuecomment-1248532873 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85KaxmJ | TomNicholas 35968931 | 2022-09-15T19:41:01Z | 2022-09-15T19:41:01Z | MEMBER |
If we're encouraging people to look at these / subclass them to create custom indexes, then they should have a repr too. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 | |
1202548224 | https://github.com/pydata/xarray/pull/6795#issuecomment-1202548224 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85HrW4A | benbovy 4160723 | 2022-08-02T13:22:24Z | 2022-08-02T13:22:24Z | MEMBER | From #6867 (https://github.com/pydata/xarray/issues/6867#issuecomment-1202535745), we might want to update the "Dimensions without coordinates" line too. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 | |
1196967258 | https://github.com/pydata/xarray/pull/6795#issuecomment-1196967258 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85HWEVa | dcherian 2448579 | 2022-07-27T16:15:57Z | 2022-07-27T16:15:57Z | MEMBER | Shall we point this at the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 | |
1186349429 | https://github.com/pydata/xarray/pull/6795#issuecomment-1186349429 | https://api.github.com/repos/pydata/xarray/issues/6795 | IC_kwDOAMm_X85GtkF1 | benbovy 4160723 | 2022-07-17T00:22:21Z | 2022-07-17T00:24:01Z | MEMBER | A few thoughts:
Like for variable data, Xarray indexes could implement
I'd skip it for the plain text DataArray / Dataset reprs (not a good information / verbosity ratio), but I'd keep it for the html repr (the index section could be collapsed by default) as well as for the
Assuming that all coordinates related to a given index are shown next to each other, we could render the inline repr for the 1st coordinate and then use a short symbol (e.g.,
I think we can keep it as-is. It helps to identify at a glance which coordinates are indexed and which aren't. And it's still relevant if we skip PandasIndex and PandasMultiIndex in the plain text DataArray / Dataset reprs. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
display the indexes in the string reprs 1306887842 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 4