home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where author_association = "MEMBER" and issue = 602218021 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 4

  • jhamman 1
  • dcherian 1
  • keewis 1
  • TomNicholas 1

issue 1

  • Make subclassing easier? · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1448964988 https://github.com/pydata/xarray/issues/3980#issuecomment-1448964988 https://api.github.com/repos/pydata/xarray/issues/3980 IC_kwDOAMm_X85WXXN8 dcherian 2448579 2023-02-28T21:46:03Z 2023-02-28T21:49:08Z MEMBER

Following this very long discussion on propagating grid information with Xarray objects, this group wants to subclass and attach unstructured grid information to their derived classes.

I invited them to the meeting tomorrow to discuss a public subclassing interface as proposed here. Come with opinions!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Make subclassing easier? 602218021
1402777128 https://github.com/pydata/xarray/issues/3980#issuecomment-1402777128 https://api.github.com/repos/pydata/xarray/issues/3980 IC_kwDOAMm_X85TnK4o TomNicholas 35968931 2023-01-24T22:30:25Z 2023-01-24T22:30:25Z MEMBER

@pydata/xarray should this feature be added to our development roadmap? It's arguably another approach to making more flexible data structures...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Make subclassing easier? 602218021
616095257 https://github.com/pydata/xarray/issues/3980#issuecomment-616095257 https://api.github.com/repos/pydata/xarray/issues/3980 MDEyOklzc3VlQ29tbWVudDYxNjA5NTI1Nw== keewis 14808389 2020-04-19T10:15:07Z 2020-04-19T10:15:07Z MEMBER

There is also #3582 where the recommendation was to wrap instead of subclassing.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Make subclassing easier? 602218021
615467263 https://github.com/pydata/xarray/issues/3980#issuecomment-615467263 https://api.github.com/repos/pydata/xarray/issues/3980 MDEyOklzc3VlQ29tbWVudDYxNTQ2NzI2Mw== jhamman 2443309 2020-04-17T21:16:36Z 2020-04-17T21:16:36Z MEMBER

Thanks @TomNicholas for opening up this issue. Just cross referencing one more issue: https://github.com/pydata/xarray/issues/1097

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Make subclassing easier? 602218021

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 28.949ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows