issue_comments
6 rows where issue = 1412926287 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- use `_repr_inline_` for indexes that define it · 6 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1284076428 | https://github.com/pydata/xarray/pull/7183#issuecomment-1284076428 | https://api.github.com/repos/pydata/xarray/issues/7183 | IC_kwDOAMm_X85MiXOM | keewis 14808389 | 2022-10-19T14:06:43Z | 2022-10-19T14:06:43Z | MEMBER | okay, let's merge this and update #7183. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use `_repr_inline_` for indexes that define it 1412926287 | |
| 1283901761 | https://github.com/pydata/xarray/pull/7183#issuecomment-1283901761 | https://api.github.com/repos/pydata/xarray/issues/7183 | IC_kwDOAMm_X85MhslB | keewis 14808389 | 2022-10-19T12:03:16Z | 2022-10-19T12:03:16Z | MEMBER | I will add that in #7185 (#6795 is also missing an entry) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use `_repr_inline_` for indexes that define it 1412926287 | |
| 1283897249 | https://github.com/pydata/xarray/pull/7183#issuecomment-1283897249 | https://api.github.com/repos/pydata/xarray/issues/7183 | IC_kwDOAMm_X85Mhreh | benbovy 4160723 | 2022-10-19T11:59:08Z | 2022-10-19T11:59:08Z | MEMBER | Looks all good to me! Do you want to add a what's new entry here or add it in #7185 with a link to this PR? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use `_repr_inline_` for indexes that define it 1412926287 | |
| 1282295471 | https://github.com/pydata/xarray/pull/7183#issuecomment-1282295471 | https://api.github.com/repos/pydata/xarray/issues/7183 | IC_kwDOAMm_X85Mbkav | benbovy 4160723 | 2022-10-18T12:19:56Z | 2022-10-18T12:19:56Z | MEMBER | Yeah I think we could let the whole line after the 1st column (coordinate names) be customized by the index. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use `_repr_inline_` for indexes that define it 1412926287 | |
| 1282275617 | https://github.com/pydata/xarray/pull/7183#issuecomment-1282275617 | https://api.github.com/repos/pydata/xarray/issues/7183 | IC_kwDOAMm_X85Mbfkh | keewis 14808389 | 2022-10-18T12:02:39Z | 2022-10-18T12:04:09Z | MEMBER | Not sure. As far as I can tell, the information that could be put in the repr would be: - the names of the wrapped variables - the index class name - any parameters passed to the constructor - parameters inferred from the data? I guess the separation very much depends on how we want to display the indexes. For now, I'd imagine something like this would be great:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use `_repr_inline_` for indexes that define it 1412926287 | |
| 1282151989 | https://github.com/pydata/xarray/pull/7183#issuecomment-1282151989 | https://api.github.com/repos/pydata/xarray/issues/7183 | IC_kwDOAMm_X85MbBY1 | benbovy 4160723 | 2022-10-18T10:11:46Z | 2022-10-18T10:11:46Z | MEMBER | Great @keewis! One question: should we let |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use `_repr_inline_` for indexes that define it 1412926287 |
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 2