pull_requests

Table actions

1 row where user = 2807085

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
762621298 PR_kwDOAMm_X84tdK1y 5880 closed 0 Alternate method using inline css to hide regular html output in an untrusted notebook mlhenderson 2807085 When using xarray in a jupyterlab notebook environment with lab extensions loading external css libraries (e.g., bootstrap), the hidden html5 attribute applied to the 'xr-wrap' div element is actually respected and cannot be escaped using a display change in the xarray included css. The html hidden attribute was weakly enforced in some browsers, but bootstrap added this rule to ensure it took effect as early as v4.0: https://github.com/twbs/bootstrap/blob/v4.0.0/scss/_reboot.scss#L480-L482 This means that not only does the normal html content inside the xr-wrap div not display in a trusted notebook environment that has this type of css rule applied from an external library, the fallback text display mechanism in the pre element does not kick in because the css block is present and sets that content to 'display: none' and so then you just get blank output in the cell when trying to display a Dataset, which is not ideal. This PR addresses the above problem and maintains a fallback display mechanism when in an untrusted notebook. In a trusted environment, the css will be loaded and the inline css for 'xr-wrap' of 'display:none' will be overridden by the embedded css style block of 'display: block !important', displaying the expected html. In an untrusted environment, the css block will be removed (not hiding the pre element) but the inline style will remain (hiding the 'xr-wrap' div element), leaving the pre text to load instead. - [x] Passes `pre-commit run --all-files` - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` 2021-10-20T18:47:19Z 2021-11-24T09:45:37Z 2021-11-13T05:16:48Z 2021-11-13T05:16:48Z efe3b1bb9f93cd92378cb859f6f4550bcdbaad72     0 192a67c7c66ae1f86733f716ce0862e87fb54b44 b79155862e154db45dff3b526c2f9e8ef303808f CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/5880  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [pull_requests] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [state] TEXT,
   [locked] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [body] TEXT,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [merged_at] TEXT,
   [merge_commit_sha] TEXT,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [draft] INTEGER,
   [head] TEXT,
   [base] TEXT,
   [author_association] TEXT,
   [auto_merge] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_pull_requests_merged_by]
    ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
    ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
    ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
    ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
    ON [pull_requests] ([user]);