issue_comments

Table actions

1 row where issue = 224846826 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • fmaussion · 1 ✖

issue 1

  • FacetGrid with independent colorbars · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
297934889 https://github.com/pydata/xarray/issues/1387#issuecomment-297934889 https://api.github.com/repos/pydata/xarray/issues/1387 MDEyOklzc3VlQ29tbWVudDI5NzkzNDg4OQ== fmaussion 10050469 2017-04-28T08:03:06Z 2017-04-28T08:03:06Z MEMBER

Seems reasonable, although this would imply quite a lot of change in the current logic. For example, facetgrids share x and/or y axis:

If there is a colorbar in between, would you like to share axes?

The current way to do what you need is to do it manually:

ds = xr.tutorial.load_dataset('air_temperature') t = ds.air.groupby('time.season').mean(dim='time') f, (ax1, ax2) = plt.subplots(1, 2, figsize=(7, 3)) t.isel(season=0).plot(ax=ax1) t.isel(season=1).plot(ax=ax2)

As you see, this messes up with the layout so a call to tight_layout() is necessary.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   FacetGrid with independent colorbars 224846826

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