home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 514142439

This data as json

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
514142439 MDExOlB1bGxSZXF1ZXN0MzMzODA1NTUy 3459 Dataset.map 5635139 closed 0     7 2019-10-29T18:46:04Z 2019-11-09T22:08:07Z 2019-11-09T21:10:23Z MEMBER   0 pydata/xarray/pulls/3459
  • [x] Helps https://github.com/pydata/xarray/issues/1251
  • [x] Tests added
  • [x] Passes black . && mypy . && flake8
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API

This is the first step towards organizing these functions a bit better, as outlined in https://github.com/pydata/xarray/issues/1251, https://github.com/pydata/xarray/issues/1618, https://github.com/pydata/xarray/pull/2674

While this one is a fairly easy decision, others are going to be harder. Open to a more methodical up-front process before we start making changes, if we think that's necessary.

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3459/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    13221727 pull

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 7 rows from issue in issue_comments
Powered by Datasette · Queries took 3.936ms · About: xarray-datasette