home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 200593854 and user = 731499 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • vnoel · 2 ✖

issue 1

  • transfer projection to implied subplots when faceting · 2 ✖

author_association 1

  • CONTRIBUTOR 2
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
272415578 https://github.com/pydata/xarray/pull/1205#issuecomment-272415578 https://api.github.com/repos/pydata/xarray/issues/1205 MDEyOklzc3VlQ29tbWVudDI3MjQxNTU3OA== vnoel 731499 2017-01-13T10:52:32Z 2017-01-13T10:52:32Z CONTRIBUTOR

As it is, the xarray code becomes tied up with cartopy. If cartopy somehow changes its syntax (e.g. by renaming the transform kw) this code won't work.

Maybe there's another, more abstract way to do this?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  transfer projection to implied subplots when faceting 200593854
272414593 https://github.com/pydata/xarray/pull/1205#issuecomment-272414593 https://api.github.com/repos/pydata/xarray/issues/1205 MDEyOklzc3VlQ29tbWVudDI3MjQxNDU5Mw== vnoel 731499 2017-01-13T10:47:28Z 2017-01-13T10:47:28Z CONTRIBUTOR

One concern I have is that it is conceivable that one might pass a transform keyword to plot() intended to interact with another library that hijacks matplotlib (i.e. not cartopy). In that case, matplotlib will get an unintended projection argument. That is a corner case though.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  transfer projection to implied subplots when faceting 200593854

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]);
Powered by Datasette · Queries took 1045.683ms · About: xarray-datasette