issues
2 rows where user = 12703555 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at ▲ | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
298822419 | MDExOlB1bGxSZXF1ZXN0MTcwMzYzMDc4 | 1930 | DOC: Plot discrete colormap with proportional colorbar | paulvija 12703555 | closed | 0 | 5 | 2018-02-21T02:36:53Z | 2018-03-01T00:05:58Z | 2018-02-27T21:19:58Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/1930 | Using 'cbar_kwargs' it is possible to extend the capabilities of colorbar ticks.
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1930/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | |||||
178501065 | MDU6SXNzdWUxNzg1MDEwNjU= | 1015 | 'levels' tick labels for discrete colormaps | paulvija 12703555 | closed | 0 | 11 | 2016-09-22T01:38:15Z | 2018-02-27T21:19:58Z | 2018-02-27T21:19:58Z | CONTRIBUTOR | Hi there, 'levels' tick labels for discrete colormaps works fine for 10 intervals and tend to shorten by itself beyond 10. This behavior may exist to make colorbar exceeding 10 intervals look tidy. However, for discrete colormaps it will be good to label the ticks for all intervals as they can be any number and not uniform. xray.version = '0.8.2' Please see the screenshots attached for a better understanding. Thanks,
Vijay Paul
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1015/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);