issue_comments

Table actions

5 rows where author_association = "CONTRIBUTOR" and user = 335567 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • Carreau · 5 ✖

author_association 1

  • CONTRIBUTOR · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
816855831 https://github.com/pydata/xarray/pull/5122#issuecomment-816855831 https://api.github.com/repos/pydata/xarray/issues/5122 MDEyOklzc3VlQ29tbWVudDgxNjg1NTgzMQ== Carreau 335567 2021-04-09T17:57:53Z 2021-04-09T17:57:53Z CONTRIBUTOR

that looks cool. Do you have a link for that project?

I just updated the readme a bit and made the repo public. Feedback welcome; though it's in an extremely alpha stage.

https://github.com/Carreau/papyri

Don't trust any of the current documentation/info right now most things are in my head. There is a currently build step necessary for the documentation; I've done it for xarray 0.17.0, so if you have another version locally it may not work.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DOC: Autoreformat all docstrings. 851917806
816013494 https://github.com/pydata/xarray/pull/5122#issuecomment-816013494 https://api.github.com/repos/pydata/xarray/issues/5122 MDEyOklzc3VlQ29tbWVudDgxNjAxMzQ5NA== Carreau 335567 2021-04-08T17:40:27Z 2021-04-08T17:40:27Z CONTRIBUTOR

Because we're already bug fans of your work!

Haha indeed.

we use napoleon which doesn't have that issue but it's still nice to keep the style consistent

Yeah, I agree numpydoc could be improved, though at the same time consistent styling is nice. And I'm working on a terminal renderer for IPython that need slightly stricter syntax.

I agree, this really is useful. Unfortunately it still seems a bit too unstable, and it is missing a few features (I'll try to open issues for those).

Looking forward to it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DOC: Autoreformat all docstrings. 851917806
652625539 https://github.com/pydata/xarray/pull/4187#issuecomment-652625539 https://api.github.com/repos/pydata/xarray/issues/4187 MDEyOklzc3VlQ29tbWVudDY1MjYyNTUzOQ== Carreau 335567 2020-07-01T20:17:36Z 2020-07-01T20:17:36Z CONTRIBUTOR

As a note I'm working on implementing zarr spec v3 in zarr-python, still deciding how we want to handle the new spec/API.

If there are any changes that you would like or dislike in an API, feedback is welcome. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Xarray open_mfdataset with engine Zarr 647804004
511236366 https://github.com/pydata/xarray/pull/1820#issuecomment-511236366 https://api.github.com/repos/pydata/xarray/issues/1820 MDEyOklzc3VlQ29tbWVudDUxMTIzNjM2Ng== Carreau 335567 2019-07-14T21:21:50Z 2019-07-14T21:21:50Z CONTRIBUTOR

Sidenote: the css is not injected at load time when the notebook is not trusted, so the REPRs may looked garbled. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   WIP: html repr 287844110
511236136 https://github.com/pydata/xarray/pull/1820#issuecomment-511236136 https://api.github.com/repos/pydata/xarray/issues/1820 MDEyOklzc3VlQ29tbWVudDUxMTIzNjEzNg== Carreau 335567 2019-07-14T21:18:08Z 2019-07-14T21:18:08Z CONTRIBUTOR

I'm just starting to look at this, was there any experiment with the html "detail" and "summary" pairs ?

They are made to do collapsible sections, and will likely allow to get rid of (some of) the UUID logic.

Here is a full example of a summary section. ``` %%html

<style> details[open] >summary > .info{ display:none; } </style>
Coordinate (hidden when expanded): Your actual nested content.

```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   WIP: html repr 287844110

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