issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 264747372 and user = 1197350 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • rabernat · 3 ✖

issue 1

  • html repr of xarray object (for the notebook) · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
546008898 https://github.com/pydata/xarray/issues/1627#issuecomment-546008898 https://api.github.com/repos/pydata/xarray/issues/1627 MDEyOklzc3VlQ29tbWVudDU0NjAwODg5OA== rabernat 1197350 2019-10-24T16:56:15Z 2019-10-24T16:56:15Z MEMBER

🎉 🍰 🍾 🏆 🏅

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr of xarray object (for the notebook) 264747372
336146728 https://github.com/pydata/xarray/issues/1627#issuecomment-336146728 https://api.github.com/repos/pydata/xarray/issues/1627 MDEyOklzc3VlQ29tbWVudDMzNjE0NjcyOA== rabernat 1197350 2017-10-12T14:02:06Z 2017-10-12T14:02:06Z MEMBER

Although this could clearly be made more fancy and complicated, I think what you have here would already be a great addition. I love the drop-down attributes (those are missing from the standard repr).

Don't hesitate to start a PR! More fanciness could always be added in the future based on user feedback.

On Thu, Oct 12, 2017 at 9:01 AM, Benoit Bovy notifications@github.com wrote:

Thanks for the feedback!

Here is a few more ideas: https://jsfiddle.net/9ab4c3tr/48/

  • main sections titles are colored so that these are more detached from the content (not sure I really like it, though),
  • subtle shade variations, notably for displaying the first values for each variable,
  • drop-downs for displaying attributes per variable if any (collapsed by default).
  • hover-effect for dimensions: highlight all variables having the hovered dimension (uses Javascript)

We might use drop-downs to display other useful information as well, such as the type of array (e.g., dask-array, in-memory numpy.array, etc...)

Fancy hover effects would be awesome indeed, although my concern is that too much hover effect would be a source of distraction.

A jupyterlab NetCDF viewer extension would be awesome too! It might also leverage phosphor's datagrid (phosphorjs/phosphor#285 https://github.com/phosphorjs/phosphor/issues/285) to explore the raw data values.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/1627#issuecomment-336127376, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJFJrhyjDbEVEz5AqUN6l2ppExwE3xiks5srg2MgaJpZM4P2LOr . 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr of xarray object (for the notebook) 264747372
335960219 https://github.com/pydata/xarray/issues/1627#issuecomment-335960219 https://api.github.com/repos/pydata/xarray/issues/1627 MDEyOklzc3VlQ29tbWVudDMzNTk2MDIxOQ== rabernat 1197350 2017-10-11T21:53:42Z 2017-10-11T21:53:42Z MEMBER

OMG this is so cool!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   html repr of xarray object (for the notebook) 264747372

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);