issue_comments
3 rows where issue = 675342733 and user = 4160723 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- constructing nested inline reprs · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
672708892 | https://github.com/pydata/xarray/issues/4324#issuecomment-672708892 | https://api.github.com/repos/pydata/xarray/issues/4324 | MDEyOklzc3VlQ29tbWVudDY3MjcwODg5Mg== | benbovy 4160723 | 2020-08-12T08:01:32Z | 2020-08-12T08:01:32Z | MEMBER | Good points @jthielen. Here's another suggestion:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
constructing nested inline reprs 675342733 | |
671941166 | https://github.com/pydata/xarray/issues/4324#issuecomment-671941166 | https://api.github.com/repos/pydata/xarray/issues/4324 | MDEyOklzc3VlQ29tbWVudDY3MTk0MTE2Ng== | benbovy 4160723 | 2020-08-11T13:17:24Z | 2020-08-11T13:17:24Z | MEMBER | Thinking more about it, I find the current repr (both text and html) already quite dense and I'm wondering if this couldn't be the opportunity to clean it a little bit. For example, the inline array repr would be only for showing the values (if directly accessible, otherwise
For any additional data/metadata, we have collapsed sections for the html repr (toggleable using the icons). For the text repr, we could have additional display options like It might be rather opposite to what you want to achieve @keewis, but I think a cleaner repr with hidden sections (or turned-off display options) by default would make sense if 80% of Xarray users are dealing mostly with numpy arrays. (sorry my comment is slightly off-topic). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
constructing nested inline reprs 675342733 | |
671925956 | https://github.com/pydata/xarray/issues/4324#issuecomment-671925956 | https://api.github.com/repos/pydata/xarray/issues/4324 | MDEyOklzc3VlQ29tbWVudDY3MTkyNTk1Ng== | benbovy 4160723 | 2020-08-11T12:48:00Z | 2020-08-11T12:48:00Z | MEMBER | It's tricky for the text repr, but for the html repr some sort of horizontal accordion would be nice, although I'd be concerned adding more complexity to the current repr (regarding both UI and HTML/CSS code). Alternatively, we could "simply" reuse the dropdown sections of each variable and add one or more sections next to the attribute and data repr ones (with their own expand icon). This could give a bit more space for fancy things and this would leave the inline space for only the highest nested array object and/or values preview if available. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
constructing nested inline reprs 675342733 |
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 1