issue_comments
6 rows where author_association = "CONTRIBUTOR" and issue = 287844110 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- WIP: html repr · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
544676254 | https://github.com/pydata/xarray/pull/1820#issuecomment-544676254 | https://api.github.com/repos/pydata/xarray/issues/1820 | MDEyOklzc3VlQ29tbWVudDU0NDY3NjI1NA== | jsignell 4806877 | 2019-10-21T19:44:52Z | 2019-10-21T19:44:52Z | CONTRIBUTOR | The last fiddle and this PR seem fairly different. Does the fiddle have the most up-to-date hierarchy or is it just somewhere where people were playing around with ideas (in which case I should see what is improved and try to pull those bits of css)? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: html repr 287844110 | |
543363463 | https://github.com/pydata/xarray/pull/1820#issuecomment-543363463 | https://api.github.com/repos/pydata/xarray/issues/1820 | MDEyOklzc3VlQ29tbWVudDU0MzM2MzQ2Mw== | jsignell 4806877 | 2019-10-17T21:10:56Z | 2019-10-17T21:10:56Z | CONTRIBUTOR | Ok thanks! I'll get cracking :) |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: html repr 287844110 | |
542766063 | https://github.com/pydata/xarray/pull/1820#issuecomment-542766063 | https://api.github.com/repos/pydata/xarray/issues/1820 | MDEyOklzc3VlQ29tbWVudDU0Mjc2NjA2Mw== | jsignell 4806877 | 2019-10-16T15:45:56Z | 2019-10-16T15:45:56Z | CONTRIBUTOR | Is there anything that I can do to help get this PR in? Are the items on the TODO list prioritized? One minor comment is that in terms of style for overflow, it might be more legible if the var_names were bolded on hover (fiddle), although that might make them look clickable. |
{ "total_count": 4, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 4, "rocket": 0, "eyes": 0 } |
WIP: html repr 287844110 | |
511236366 | https://github.com/pydata/xarray/pull/1820#issuecomment-511236366 | https://api.github.com/repos/pydata/xarray/issues/1820 | MDEyOklzc3VlQ29tbWVudDUxMTIzNjM2Ng== | Carreau 335567 | 2019-07-14T21:21:50Z | 2019-07-14T21:21:50Z | CONTRIBUTOR | Sidenote: the css is not injected at load time when the notebook is not trusted, so the REPRs may looked garbled. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: html repr 287844110 | |
511236136 | https://github.com/pydata/xarray/pull/1820#issuecomment-511236136 | https://api.github.com/repos/pydata/xarray/issues/1820 | MDEyOklzc3VlQ29tbWVudDUxMTIzNjEzNg== | Carreau 335567 | 2019-07-14T21:18:08Z | 2019-07-14T21:18:08Z | CONTRIBUTOR | I'm just starting to look at this, was there any experiment with the html "detail" and "summary" pairs ? They are made to do collapsible sections, and will likely allow to get rid of (some of) the UUID logic. Here is a full example of a summary section. ``` %%html <style> details[open] >summary > .info{ display:none; } </style>Coordinate (hidden when expanded):Your actual nested content.``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: html repr 287844110 | |
477574320 | https://github.com/pydata/xarray/pull/1820#issuecomment-477574320 | https://api.github.com/repos/pydata/xarray/issues/1820 | MDEyOklzc3VlQ29tbWVudDQ3NzU3NDMyMA== | StanczakDominik 11289391 | 2019-03-28T12:28:33Z | 2019-03-28T12:28:33Z | CONTRIBUTOR | I just came by to say that the attached sample notebook is very, very pretty, and I would love to see this line of work continue! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: html repr 287844110 |
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 3