issue_comments

Table actions

5 rows where issue = 110820316 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 3

issue 1

  • Don't squeeze DataArray before plotting · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1500937954 https://github.com/pydata/xarray/issues/620#issuecomment-1500937954 https://api.github.com/repos/pydata/xarray/issues/620 IC_kwDOAMm_X85Zdn7i headtr1ck 43316012 2023-04-08T17:20:35Z 2023-04-08T17:20:50Z COLLABORATOR

Reviving this ancient issue here. We could add a deprecation cycle and issue a warning for dimensions with size 1.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't squeeze DataArray before plotting 110820316
881582747 https://github.com/pydata/xarray/issues/620#issuecomment-881582747 https://api.github.com/repos/pydata/xarray/issues/620 IC_kwDOAMm_X840i-Kb shoyer 1217238 2021-07-16T16:48:59Z 2021-07-16T16:48:59Z MEMBER

I would support a breaking change to Xarray's plotting methods here to remove squeezing. These sort of inconsistencies are really indeed annoying to program around!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't squeeze DataArray before plotting 110820316
881575310 https://github.com/pydata/xarray/issues/620#issuecomment-881575310 https://api.github.com/repos/pydata/xarray/issues/620 IC_kwDOAMm_X840i8WO dschneiderch 7461221 2021-07-16T16:35:33Z 2021-07-16T16:35:33Z NONE

I already mentioned this issue in a couple others but, as an FYI, I ran into this trying to write a plotting function that accepts a dataarray and **kwargs. It's a bit annoying to have to deal with the dataarray differently depending on whether the facetting variable has length == 1 or >1.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't squeeze DataArray before plotting 110820316
459316993 https://github.com/pydata/xarray/issues/620#issuecomment-459316993 https://api.github.com/repos/pydata/xarray/issues/620 MDEyOklzc3VlQ29tbWVudDQ1OTMxNjk5Mw== stale[bot] 26384082 2019-01-31T11:52:15Z 2019-01-31T11:52:15Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't squeeze DataArray before plotting 110820316
147133468 https://github.com/pydata/xarray/issues/620#issuecomment-147133468 https://api.github.com/repos/pydata/xarray/issues/620 MDEyOklzc3VlQ29tbWVudDE0NzEzMzQ2OA== shoyer 1217238 2015-10-10T23:02:03Z 2015-10-10T23:02:03Z MEMBER

I see two options: 1. Squeeze after the row/col selection logic. 2. Raise an error if someone attempts to plot a (N, 1) plot as 2D.

1 might actually be preferable to not squeezing at all.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't squeeze DataArray before plotting 110820316

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