profile
viewpoint
Brandon Dail aweary @discord Austin, TX brandondail.com a11y at @discord. previously @facebook, @FormidableLabs. Helped maintain @reactjs once upon a time.

aweary/alder 170

A minimal implementation of the UNIX tree command with colors!

aweary/babel-rust 7

A source-to-source JavaScript compiler written in Rust. Not for production use.

aweary/assert-report 3

A barebones test reporter in ~1.5kb with zero dependencies

aweary/cached-validations 3

Create validation functions that cache results

aweary/1x.engineer 1

The official website of 1x Engineers around the world

aweary/awesome-redux 1

Awesome list of Redux examples and middlewares

startednvaccess/nvda

started time in a day

startedJavacord/Javacord

started time in 2 days

startedjakehilborn/displayplacer

started time in 4 days

startedaweary/AccessibilityNodeInfoRepoProject

started time in 8 days

startedaweary/AccessibilityNodeInfoRepoProject

started time in 9 days

push eventaweary/AccessibilityNodeInfoRepoProject

Brandon Dail

commit sha 8852ceca84caeba51f880bb73d5e50169137e528

Create README.md

view details

push time in 9 days

create barnchaweary/AccessibilityNodeInfoRepoProject

branch : master

created branch time in 9 days

created repositoryaweary/AccessibilityNodeInfoRepoProject

created time in 9 days

startedgleam-lang/gleam

started time in 11 days

PR closed aweary/tinytime

Bump handlebars from 4.0.6 to 4.7.6 dependencies

Bumps handlebars from 4.0.6 to 4.7.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.6 - April 3rd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1672">#1672</a> - Switch cmd parser to latest minimist (<a href="https://api.github.com/users/dougwilson">@dougwilson</a></li> </ul> <p>Compatibility notes:</p> <ul> <li>Restored Node.js compatibility</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.5...v4.7.6">Commits</a></p> <h2>v4.7.5 - April 2nd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><del>Node.js version support has been changed to v6+</del> Reverted in 4.7.6</li> </ul> <p>Compatibility notes:</p> <ul> <li><del>Node.js < v6 is no longer supported</del> Reverted in 4.7.6</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.4...v4.7.5">Commits</a></p> <h2>v4.7.4 - April 1st, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1666">#1666</a> - Replaced minimist with yargs for handlebars CLI (<a href="https://api.github.com/users/aorinevo">@aorinevo</a>, <a href="https://api.github.com/users/AviVahl">@AviVahl</a> & <a href="https://api.github.com/users/fabb">@fabb</a>)</li> </ul> <p>Compatibility notes:</p> <ul> <li>No incompatibilities are to be expected</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.3...v4.7.4">Commits</a></p> <h2>v4.7.3 - February 5th, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1644">#1644</a> - Download links to aws broken on handlebarsjs.com - access denied (<a href="https://api.github.com/users/Tea56">@Tea56</a>)</li> <li>Fix spelling and punctuation in changelog - d78cc73</li> </ul> <p>Bugfixes:</p> <ul> <li>Add Type Definition for Handlebars.VERSION, Fixes <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1647">#1647</a> - 4de51fe</li> <li>Include Type Definition for runtime.js in Package - a32d05f</li> </ul> <p>Compatibility notes:</p> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e6ad93ea01bcde1f8ddaa4b4ebe572dd616abfaa"><code>e6ad93e</code></a> v4.7.6</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/2bf4fc6fd3ae3d8f076d628653f284d85faebeb4"><code>2bf4fc6</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b64202bc9197307bd785a58693e3820eb9bb41a8"><code>b64202b</code></a> Update release-notes.md</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/c2f1e6203178918569f085e12afdb762cae17fb0"><code>c2f1e62</code></a> Switch cmd parser to latest minimist</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/08e9a11a34c3ad8387a0b85b1334f97cab85191a"><code>08e9a11</code></a> Revert "chore: set Node.js compatibility to v6+"</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/1fd2edee2a12fb228061fcde807905c6b14339c4"><code>1fd2ede</code></a> v4.7.5</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3c9c2f5cf29cf10f54d5fe4daca6b24b65f0adcf"><code>3c9c2f5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/16487a088e13f4d52c6fd6610b9ec71c4a51be8a"><code>16487a0</code></a> chore: downgrade yargs to v14</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/309d2b49a11628d2a8f052c5587e7459968cd705"><code>309d2b4</code></a> chore: set Node.js compatibility to v6+</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/645ac73844918668f9a2f41e49b7cb18ce5abf36"><code>645ac73</code></a> test: fix integration tests</li> <li>Additional commits viewable in <a href="https://github.com/wycats/handlebars.js/compare/v4.0.6...v4.7.6">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~erisds">erisds</a>, a new releaser for handlebars since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+455 -32

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump lodash from 4.17.4 to 4.17.19 dependencies

Bumps lodash from 4.17.4 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.4...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+430 -7

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump standard-version from 4.4.0 to 8.0.1 dependencies

Bumps standard-version from 4.4.0 to 8.0.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/conventional-changelog/standard-version/releases">standard-version's releases</a>.</em></p> <blockquote> <h2>standard-version v8.0.1</h2> <h3>Bug Fixes</h3> <ul> <li><strong>deps:</strong> update dependency conventional-changelog to v3.1.21 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/586">#586</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/fd456c995f3f88497fbb912fb8aabb8a42d97dbb">fd456c9</a>)</li> <li><strong>deps:</strong> update dependency conventional-changelog-conventionalcommits to v4.3.0 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/587">#587</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/b3b5eedea3eaf062d74d1004a55a0a6b1e3ca6c6">b3b5eed</a>)</li> <li><strong>deps:</strong> update dependency conventional-recommended-bump to v6.0.9 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/588">#588</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/d4d2ac2a99c095227118da795e1c9e19d06c9a0a">d4d2ac2</a>)</li> <li><strong>deps:</strong> update dependency git-semver-tags to v4 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/589">#589</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/a0f0e813b2be4a2065600a19075fda4d6f331ef8">a0f0e81</a>)</li> <li>Vulnerability Report GHSL-2020-11101 (<a href="https://www.github.com/conventional-changelog/standard-version/commit/9d978ac9d4f64be4c7b9d514712ab3757732d561">9d978ac</a>)</li> </ul> <h2>standard-version v8.0.0</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li><code>composer.json</code> and <code>composer.lock</code> will no longer be read from or bumped by default. If you need to obtain a version or write a version to these files, please use <code>bumpFiles</code> and/or <code>packageFiles</code> options accordingly.</li> </ul> <h3>Bug Fixes</h3> <ul> <li>composer.json and composer.lock have been removed from default package and bump files. (<a href="https://www.github.com/conventional-changelog/standard-version/commit/c934f3a38da4e7234d9dba3b2405f3b7e4dc5aa8">c934f3a</a>), closes <a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/495">#495</a> <a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/394">#394</a></li> <li><strong>deps:</strong> update dependency conventional-changelog to v3.1.18 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/510">#510</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/e6aeb779fe53ffed2a252e6cfd69cfcb786b9ef9">e6aeb77</a>)</li> <li><strong>deps:</strong> update dependency yargs to v15.1.0 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/518">#518</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/8f36f9e073119fcbf5ad843237fb06a4ca42a0f9">8f36f9e</a>)</li> <li><strong>deps:</strong> update dependency yargs to v15.3.1 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/559">#559</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/d98cd4674b4d074c0b7f4d50d052ae618cf494c6">d98cd46</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/conventional-changelog/standard-version/blob/master/CHANGELOG.md">standard-version's changelog</a>.</em></p> <blockquote> <h3><a href="https://www.github.com/conventional-changelog/standard-version/compare/v8.0.0...v8.0.1">8.0.1</a> (2020-07-12)</h3> <h3>Bug Fixes</h3> <ul> <li><strong>deps:</strong> update dependency conventional-changelog to v3.1.21 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/586">#586</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/fd456c995f3f88497fbb912fb8aabb8a42d97dbb">fd456c9</a>)</li> <li><strong>deps:</strong> update dependency conventional-changelog-conventionalcommits to v4.3.0 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/587">#587</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/b3b5eedea3eaf062d74d1004a55a0a6b1e3ca6c6">b3b5eed</a>)</li> <li><strong>deps:</strong> update dependency conventional-recommended-bump to v6.0.9 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/588">#588</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/d4d2ac2a99c095227118da795e1c9e19d06c9a0a">d4d2ac2</a>)</li> <li><strong>deps:</strong> update dependency git-semver-tags to v4 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/589">#589</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/a0f0e813b2be4a2065600a19075fda4d6f331ef8">a0f0e81</a>)</li> <li>Vulnerability Report GHSL-2020-11101 (<a href="https://www.github.com/conventional-changelog/standard-version/commit/9d978ac9d4f64be4c7b9d514712ab3757732d561">9d978ac</a>)</li> </ul> <h2><a href="https://www.github.com/conventional-changelog/standard-version/compare/v7.1.0...v8.0.0">8.0.0</a> (2020-05-06)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li><code>composer.json</code> and <code>composer.lock</code> will no longer be read from or bumped by default. If you need to obtain a version or write a version to these files, please use <code>bumpFiles</code> and/or <code>packageFiles</code> options accordingly.</li> </ul> <h3>Bug Fixes</h3> <ul> <li>composer.json and composer.lock have been removed from default package and bump files. (<a href="https://www.github.com/conventional-changelog/standard-version/commit/c934f3a38da4e7234d9dba3b2405f3b7e4dc5aa8">c934f3a</a>), closes <a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/495">#495</a> <a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/394">#394</a></li> <li><strong>deps:</strong> update dependency conventional-changelog to v3.1.18 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/510">#510</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/e6aeb779fe53ffed2a252e6cfd69cfcb786b9ef9">e6aeb77</a>)</li> <li><strong>deps:</strong> update dependency yargs to v15.1.0 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/518">#518</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/8f36f9e073119fcbf5ad843237fb06a4ca42a0f9">8f36f9e</a>)</li> <li><strong>deps:</strong> update dependency yargs to v15.3.1 (<a href="https://www.github-redirect.dependabot.com/conventional-changelog/standard-version/issues/559">#559</a>) (<a href="https://www.github.com/conventional-changelog/standard-version/commit/d98cd4674b4d074c0b7f4d50d052ae618cf494c6">d98cd46</a>)</li> </ul> <h2><a href="https://github.com/conventional-changelog/standard-version/compare/v7.0.1...v7.1.0">7.1.0</a> (2019-12-08)</h2> <h3>Features</h3> <ul> <li>Adds support for <code>header</code> (--header) configuration based on the spec. (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/364">#364</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/ba80a0c27029f54c751fe845560504925b45eab8">ba80a0c</a>)</li> <li>custom 'bumpFiles' and 'packageFiles' support (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/372">#372</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/564d9482a459d5d7a2020c2972b4d39167ded4bf">564d948</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>deps:</strong> update dependency conventional-changelog to v3.1.15 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/479">#479</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/492e72192ebf35d7c58c00526b1e6bd2abac7f13">492e721</a>)</li> <li><strong>deps:</strong> update dependency conventional-changelog-conventionalcommits to v4.2.3 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/496">#496</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/bc606f8e96bcef1d46b28305622fc76dfbf306cf">bc606f8</a>)</li> <li><strong>deps:</strong> update dependency conventional-recommended-bump to v6.0.5 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/480">#480</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/1e1e215a633963188cdb02be1316b5506e3b99b7">1e1e215</a>)</li> <li><strong>deps:</strong> update dependency yargs to v15 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/484">#484</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/35b90c3f24cfb8237e94482fd20997900569193e">35b90c3</a>)</li> <li>use require.resolve for the default preset (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/465">#465</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/d55737239530f5eee684e9cbf959f7238d609fd4">d557372</a>)</li> <li><strong>deps:</strong> update dependency detect-newline to v3.1.0 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/482">#482</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/04ab36a12be58915cfa9c60771890e074d1f5685">04ab36a</a>)</li> <li><strong>deps:</strong> update dependency figures to v3.1.0 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/468">#468</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/63300a935c0079fd03e8e1acc55fd5b1dcea677f">63300a9</a>)</li> <li><strong>deps:</strong> update dependency git-semver-tags to v3.0.1 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/485">#485</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/9cc188cbb84ee3ae80d5e66f5c54727877313b14">9cc188c</a>)</li> <li><strong>deps:</strong> update dependency yargs to v14.2.1 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/483">#483</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/dc1fa6170ffe12d4f8b44b70d23688a64d2ad0fb">dc1fa61</a>)</li> <li><strong>deps:</strong> update dependency yargs to v14.2.2 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/488">#488</a>) (<a href="https://github.com/conventional-changelog/standard-version/commit/ecf26b6fc9421a78fb81793c4a932f579f7e9d4a">ecf26b6</a>)</li> </ul> <h3><a href="https://github.com/conventional-changelog/standard-version/compare/v7.0.0...v7.0.1">7.0.1</a> (2019-11-07)</h3> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/conventional-changelog/standard-version/commit/57e4e25d83552d225cf96e1dfc50e6042a2f7f6c"><code>57e4e25</code></a> chore: release 8.0.1 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/611">#611</a>)</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/58105e126fd4392b5b23246a90a8c51a05ffded7"><code>58105e1</code></a> chore: Adds basic issue templates (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/613">#613</a>)</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/9d978ac9d4f64be4c7b9d514712ab3757732d561"><code>9d978ac</code></a> fix: Vulnerability Report GHSL-2020-11101</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/267d78dcb3bef90ad4dcbbafd2e77739efacdf37"><code>267d78d</code></a> chore: stop pinning deps (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/615">#615</a>)</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/da84ec4b44f7d45c3e06a93e24b17ee43b988992"><code>da84ec4</code></a> test(windows): skip mock-git tests for Windows (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/616">#616</a>)</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/871201ff8de6091d4b9b2ce9bf8611a1fc2f7836"><code>871201f</code></a> Merge pull request from GHSA-7xcx-6wjh-7xp2</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/a0f0e813b2be4a2065600a19075fda4d6f331ef8"><code>a0f0e81</code></a> fix(deps): update dependency git-semver-tags to v4 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/589">#589</a>)</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/fd456c995f3f88497fbb912fb8aabb8a42d97dbb"><code>fd456c9</code></a> fix(deps): update dependency conventional-changelog to v3.1.21 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/586">#586</a>)</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/b3b5eedea3eaf062d74d1004a55a0a6b1e3ca6c6"><code>b3b5eed</code></a> fix(deps): update dependency conventional-changelog-conventionalcommits to v4...</li> <li><a href="https://github.com/conventional-changelog/standard-version/commit/d4d2ac2a99c095227118da795e1c9e19d06c9a0a"><code>d4d2ac2</code></a> fix(deps): update dependency conventional-recommended-bump to v6.0.9 (<a href="https://github-redirect.dependabot.com/conventional-changelog/standard-version/issues/588">#588</a>)</li> <li>Additional commits viewable in <a href="https://github.com/conventional-changelog/standard-version/compare/v4.4.0...v8.0.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~oss-bot">oss-bot</a>, a new releaser for standard-version since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+855 -7

0 comment

2 changed files

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump marked from 0.3.6 to 0.3.19 dependencies

Bumps marked from 0.3.6 to 0.3.19. <details> <summary>Release notes</summary>

Sourced from marked's releases.

0.3.18 minified required new release

0.3.18 did not have changes to min.

Minor fixes and updated docs

  • Supported Markdown flavors: CommonMark 0.28 and GitHub Flavored Markdown 0.28
  • Updates to our CI pipeline; we're all green! #1098 with the caveat that there is a test that needs to get sorted (help us out #1092)
  • Start ordered lists using the initial numbers from markdown lists (#1144)
  • Added GitHub Pages site for documentation https://marked.js.org/ (#1138)

Processes and tools

  • The elephant in the room: A security vulnerability was discovered and fixed. Please note, if something breaks due to these changes, it was not our intent, and please let us know by submitting a PR or issue to course correct (the nature of the zero-major release and having security as a number one priority) #1083
  • The other elephant in the room: We missed publishing a 0.3.16 release to GitHub; so, trying to make up for that a bit.
  • Updates to the project documentation and operations, you should check it out, just start with the README and you should be good.
  • New release PR template available #1076
  • Updates to default PR and Issue templates #1076
  • Lint checks + tests + continuous integration using Travis #1020
  • Updated testing output #1085 & #1087

Fix capturing parens

Fixes unintended breaking change from v0.3.14

New year, new home

  • Marked has a new home under the MarkedJS org! Other advances soon to come.
  • Updated minifier.
  • Various parser fixes

New Year, new Marked!

  • Addresses issue where some users might not have been able to update due to missing use strict #991
  • Parser fix #977
  • New way to perform tests with options and running individual tests #1002
  • Improved test cases
  • Improved links

Merry XSSmas

We think with this version we have addressed most, if not all, known security vulnerabilities. If you find more, please let us know.

XSS

Should fix XSS issue discovered. </details> <details> <summary>Commits</summary>

This version was pushed to npm by amidknight, a new releaser for marked since your current version. </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+430 -7

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump stringstream from 0.0.5 to 0.0.6 dependencies

Bumps stringstream from 0.0.5 to 0.0.6. <details> <summary>Commits</summary>

  • fee31c5 0.0.6
  • 2f4a9d4 Merge pull request #9 from mhart/fix-buffer-constructor-vuln
  • afbc744 Ensure data is not a number in Buffer constructor
  • See full diff in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+430 -7

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump is-my-json-valid from 2.15.0 to 2.20.0 dependencies

Bumps is-my-json-valid from 2.15.0 to 2.20.0. <details> <summary>Commits</summary>

  • 60111f4 2.20.0
  • 8c11f77 Merge pull request #175 from LinusU/meta
  • b6d9b3f Cleanup package metadata
  • dcea5be 2.19.0
  • 1712811 Merge pull request #171 from mafintosh/ts-nullable
  • fad4c91 Add nullable types to TypeScript typings
  • 484197f Add test for nested object in typings
  • 4bec868 Merge pull request #168 from mafintosh/ts-oneof
  • e8c30d5 Add support for "oneOf" to TypeScript typings
  • 7160756 Merge pull request #167 from mafintosh/ts-required
  • Additional commits viewable in compare view </details> <details> <summary>Maintainer changes</summary>

This version was pushed to npm by linusu, a new releaser for is-my-json-valid since your current version. </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+442 -12

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump js-yaml from 3.7.0 to 3.13.1 dependencies

Bumps js-yaml from 3.7.0 to 3.13.1. <details> <summary>Changelog</summary>

Sourced from js-yaml's changelog.

[3.13.1] - 2019-04-05

Security

  • Fix possible code execution in (already unsafe) .load(), #480.

[3.13.0] - 2019-03-20

Security

  • Security fix: safeLoad() can hang when arrays with nested refs used as key. Now throws exception for nested arrays. #475.

[3.12.2] - 2019-02-26

Fixed

  • Fix noArrayIndent option for root level, #468.

[3.12.1] - 2019-01-05

Added

  • Added noArrayIndent option, #432.

[3.12.0] - 2018-06-02

Changed

  • Support arrow functions without a block statement, #421.

[3.11.0] - 2018-03-05

Added

  • Add arrow functions suport for !!js/function.

Fixed

  • Fix dump in bin/octal/hex formats for negative integers, #399.

[3.10.0] - 2017-09-10

Fixed

  • Fix condenseFlow output (quote keys for sure, instead of spaces), #371, #370.
  • Dump astrals as codepoints instead of surrogate pair, #368.

[3.9.1] - 2017-07-08

Fixed

  • Ensure stack is present for custom errors in node 7.+, #351.

[3.9.0] - 2017-07-08

Added

  • Add condenseFlow option (to create pretty URL query params), #346.

Fixed

</tr></table> ... (truncated) </details> <details> <summary>Commits</summary>

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+438 -11

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump diff from 3.2.0 to 3.5.0 dependencies

Bumps diff from 3.2.0 to 3.5.0. <details> <summary>Changelog</summary>

Sourced from diff's changelog.

v3.5.0 - March 4th, 2018

  • Omit redundant slice in join method of diffArrays - 1023590
  • Support patches with empty lines - fb0f208
  • Accept a custom JSON replacer function for JSON diffing - 69c7f0a
  • Optimize parch header parser - 2aec429
  • Fix typos - e89c832

Commits

v3.4.0 - October 7th, 2017

  • #183 - Feature request: ability to specify a custom equality checker for diffArrays
  • #173 - Bug: diffArrays gives wrong result on array of booleans
  • #158 - diffArrays will not compare the empty string in array?
  • comparator for custom equality checks - 30e141e
  • count oldLines and newLines when there are conflicts - 53bf384
  • Fix: diffArrays can compare falsey items - 9e24284
  • Docs: Replace grunt with npm test - 00e2f94

Commits

v3.3.1 - September 3rd, 2017

  • #141 - Cannot apply patch because my file delimiter is "/r/n" instead of "/n"
  • #192 - Fix: Bad merge when adding new files (#189)
  • correct spelling mistake - 21fa478

Commits

v3.3.0 - July 5th, 2017

  • #114 - /patch/merge not exported
  • Gracefully accept invalid newStart in hunks, same as patch(1) does. - d8a3635
  • Use regex rather than starts/ends with for parsePatch - 6cab62c
  • Add browser flag - e64f674
  • refactor: simplified code a bit more - 8f8e0f2
  • refactor: simplified code a bit - b094a6f
  • fix: some corrections re ignoreCase option - 3c78fd0
  • ignoreCase option - 3cbfbb5
  • Sanitize filename while parsing patches - 2fe8129
  • Added better installation methods - aced50b
  • Simple export of functionality - 8690f31

Commits </details> <details> <summary>Commits</summary>

  • e9ab948 v3.5.0
  • b73884c Update release notes
  • 8953021 Update release notes
  • 1023590 Omit redundant slice in join method of diffArrays
  • c72ef4a Add missing test coverage
  • b9ef24f Support patches with empty lines
  • 10aaabb Support patches with empty lines
  • 196d3aa Support patches with empty lines
  • e24d789 Support patches with empty lines
  • 8616a02 Support patches with empty lines
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+430 -7

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

PR closed aweary/tinytime

Bump sshpk from 1.10.2 to 1.16.1 dependencies

Bumps sshpk from 1.10.2 to 1.16.1. <details> <summary>Release notes</summary>

Sourced from sshpk's releases.

v1.16.1

  • Fixes for #60 (correctly encoding certificates with expiry dates >=2050), #62 (accepting PKCS#8 EC private keys with missing public key parts)

v1.16.0

  • Add support for SPKI fingerprints, PuTTY PPK format (public-key only for now), PKCS#8 PBKDF2 encrypted private keys
  • Fix for #48

v1.15.2

  • New API for accessing x509 extensions in certificates
  • Fixes for #52, #50

v1.14.1

  • Remove all remaining usage of jodid25519 (abandoned dep)
  • Add support for DNSSEC key format
  • Add support for Ed25519 keys in PEM format (according to draft-curdle-pkix)
  • Fixes for X.509 encoding issues (asn.1 NULLs in RSA certs, cert string type mangling)
  • Performance issues parsing long SSH public keys

v1.13.0

  • Support SSH-format rsa-sha2-256 signatures (e.g. so the SSH agent can sign using RSA-SHA256)

v1.12.0

  • Support for generating ECDSA keys using generatePrivateKey()
  • Minimum for sshpk-agent to be able to sign new certificates using an agent key

v1.11.0

  • Added support for X.509 extKeyUsage </details> <details> <summary>Commits</summary>

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+450 -27

0 comment

1 changed file

dependabot[bot]

pr closed time in 12 days

startednodejs/undici

started time in 14 days

startedninenines/cowboy

started time in 16 days

starteddiscord/semaphore

started time in 16 days

startedgevent/gevent

started time in 20 days

starteddiscord/lilliput

started time in 20 days

startedhkgumbs/codec-beam

started time in 23 days

startedlexhide/xandra

started time in 23 days

startedQwe1rty/distributed_systems_notes

started time in 24 days

starteddatastax/cpp-driver

started time in a month

startedAmanieu/parking_lot

started time in a month

startedKDE/heaptrack

started time in a month

startedruffle-rs/ruffle

started time in a month

startedjessegrosjean/jwalk

started time in a month

startedrayon-rs/rayon

started time in a month

startedtailhook/libmount

started time in a month

startedreactjs/react-gradual-upgrade-demo

started time in a month

push eventaweary/OverlappingPanels

Brandon Dail

commit sha 6f5e15cb5b53f37f5c7edd01c6da735808f5d6f3

Hide center panel content from TalkBack when its closed

view details

push time in 2 months

push eventaweary/OverlappingPanels

Donald Chen

commit sha 32c70178d1cc621a6a18bcc5ddcd625cba8b4218

don't treat available dependency upgrades as errors (#19)

view details

Brandon Dail

commit sha 0752e9980a9f0b2cce3552c10cb26bd2592f19de

Hide center panel content from TalkBack when its closed

view details

push time in 2 months

pull request commentdiscord/OverlappingPanels

Hide center panel content from TalkBack when its closed

cc @AndyG

aweary

comment created time in 2 months

pull request commentdiscord/OverlappingPanels

Hide center panel content from TalkBack when its closed

cc @faultyserver

aweary

comment created time in 2 months

PR opened discord/OverlappingPanels

Hide center panel content from TalkBack when its closed

Before this change TalkBack would consider the center panel content visible when the start/end panels were expanded, causing it to traverse what was essentially offscreen content. This changes it so that the center panel's content is hidden from TalkBack when the center panel is closed.

+9 -0

0 comment

1 changed file

pr created time in 2 months

create barnchaweary/OverlappingPanels

branch : a11y/hide-center-panel

created branch time in 2 months

fork aweary/OverlappingPanels

Overlapping Panels is a gestures-driven navigation UI library for Android

fork in 2 months

startedFlipkart/recyclerlistview

started time in 2 months

starteddiscord/OverlappingPanels

started time in 2 months

pull request commentnetlify/million-devs

Disable animations by default for users with reduce motion enabled

@zachleat fixed!

aweary

comment created time in 2 months

push eventaweary/million-devs

Brandon Dail

commit sha c04170eb3de52a96ca968a148d93fb21c429fcd8

use .matches

view details

push time in 2 months

create barnchaweary/million-devs

branch : reduce-motion

created branch time in 2 months

fork aweary/million-devs

Microsite for the 1 Million Developers announcement.

https://million-devs.netlify.com/

fork in 2 months

issue openednetlify/million-devs

Animations should be disabled when prefers-reduced-motion is set to reduce

It's awesome that the animations are toggle-able, but for users who have set their system preferences to reduce motion they should probably be disabled by default.

You can check for that with the prefers-reduced-motion: reduce media query

created time in 2 months

issue commentfacebook/react

Bug: React.Lazy not working on Firefox, with HTTPS

Yeah, React has no part in the HTTP request that your Promise is making. I recommend checking out the list of great support resources listed in the docs: Where to Get Support.

master117

comment created time in 2 months

issue closedfacebook/react

Bug: React.Lazy not working on Firefox, with HTTPS

<!-- Please provide a clear and concise description of what the bug is. Include screenshots if needed. Please test using the latest version of the relevant React packages to make sure your issue has not already been fixed. -->

I have a bit of an odd Issue. I'm using React.lazy to load stylesheets based on what page a user is on. Since they cancel each other out I only want one of them to be loaded / I want them to be split. This works in all browsers and both with HTTPS and HTTP. Except in Firefox with HTTPS. My certificates are self-signed, so firefox is having some issues with them, but I added exceptions for them.

React version: >16.11 Firefox Version: 78.0.2

Steps To Reproduce

Since this is likely a HTTPS certificates issue I can't produce a minimal example easily. <!-- Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Issues without reproduction steps or code examples may be immediately closed as not actionable. -->

I'm using an implementation of React Lazy that lets me retry on failure, but it doesn't work either way:

/**
 * Tries lazy loading, retries 4 times on failure with a pause of 1 second inbetween
 */
const retryLazyLoad = (fn: () => Promise<any>, retriesLeft = 5, interval = 1000): Promise<{ default: ComponentType<any>; }> => {
  // Return function as promise
  return new Promise((resolve, reject) => {
    fn()
      .then(resolve)
      .catch((error) => {
        console.log(error);
        setTimeout(() => {        
          // On error either reject or retry
          if(retriesLeft === 1) {
            // reject('maximum retries exceeded');
            console.log("Maximum retries for lazy loading themes exceeded!");
            reject(error);
            return;
          }

          // Passing on "reject" is the important part
          retryLazyLoad(fn, retriesLeft - 1, interval).then(resolve, reject);
        }, interval);
      });
  });
}

/**
 * The theme components only imports it's theme CSS-file. These components are lazy
 * loaded, to enable "code splitting" (in order to avoid the themes being bundled together)
 */
const RgaTheme = React.lazy(() => retryLazyLoad(() => import('../../Pages/Content/Graph/RgaTheme')));
const RlmTheme = React.lazy(() => retryLazyLoad(() => import('../../Pages/Content/List/RlmTheme')));

const ThemeSelector: React.FunctionComponent<IThemeSeletorProps> = (props) => {
  return (
    <React.Fragment>
      {/* Conditionally render theme, based on the current seleced module*/}
      <React.Suspense fallback={<ProgressSpinner />}>
        {props.module === "graph" ? <RgaTheme /> : <RlmTheme />}
      </React.Suspense>
      {/* Render children immediately */}
      {props.children}
    </React.Fragment>
  );
};

The current behavior

React Lazy runs into an exception when retrieving the css chunk 4.

Unbenannt3

Unbenannt2

The requests are not even shown in firefox,

Unbenannt4

but in firefox developer edition.

Unbenannt

The requests being seen and marked as 200 and the fact that it works in all other browsers leads me to believe there is an issue between firefox + https and React.lazy.

The expected behavior

React.lazy should have no issue loading my css.

Please let me know if I can provide additional details.

closed time in 2 months

master117

issue commentfacebook/react

useState

请使用请求的信息填写问题模板,或查看我们的支持资源以获取帮助:https://zh-hans.reactjs.org/community/support.html

wjw760306378

comment created time in 2 months

issue closedfacebook/react

useState

useState在每次组件re-render的时候都会生成新的值,为什么把这个值传递给子组件,子组件不会re-render

closed time in 2 months

wjw760306378

issue closedfacebook/react

The props reference remains in 'FiberNode' after the component is unloaded

React version: 16.13.1

Description I tried to uninstall a component and found that the props reference for that component is still in 'FiberNode' after uninstalling. Why is this happening and who can help with this?

closed time in 2 months

rocky-one

issue commentfacebook/react

The props reference remains in 'FiberNode' after the component is unloaded

Hey @rocky-one, some data might be retained for a short period. Eventually React will delete those references. There are some known issues with memory leaks that might affect what you're seeing as well.

If you think you're seeing a new memory issue please follow up with a code sample that reproduces the problem and we can investigate. Thanks!

rocky-one

comment created time in 2 months

Pull request review commentfacebook/react

Add postTask browser scheduler implementation

  * LICENSE file in the root directory of this source tree.  */ -import {enableIsInputPending} from '../SchedulerFeatureFlags';+// Capture local references to native APIs, in case a polyfill overrides them.+const date = window.Date;+const perf = window.performance;+const setTimeout = window.setTimeout;+const clearTimeout = window.clearTimeout;++// This check should be done upstream but do it again for a clear failure message.+if (global.scheduler === undefined || global.scheduler.postTask === undefined) {+  throw new Error('Cannot use postTask Scheduler without global.scheduler');+} -export let requestHostCallback;-export let cancelHostCallback;-export let requestHostTimeout;-export let cancelHostTimeout;-export let shouldYieldToHost;-export let requestPaint;-export let getCurrentTime;-export let forceFrameRate;+function postTask(callback) {+  // Use experimental Chrome Scheduler postTask API.+  global.scheduler.postTask(callback);+} -if (-  // If Scheduler runs in a non-DOM environment, it falls back to a naive-  // implementation using setTimeout.-  typeof window === 'undefined' ||-  // Check if MessageChannel is supported, too.-  typeof MessageChannel !== 'function'-) {-  // If this accidentally gets imported in a non-browser environment, e.g. JavaScriptCore,-  // fallback to a naive implementation.-  let _callback = null;-  let _timeoutID = null;-  const _flushCallback = function() {-    if (_callback !== null) {-      try {-        const currentTime = getCurrentTime();-        const hasRemainingTime = true;-        _callback(hasRemainingTime, currentTime);-        _callback = null;-      } catch (e) {-        setTimeout(_flushCallback, 0);-        throw e;-      }-    }-  };-  const initialTime = Date.now();-  getCurrentTime = function() {-    return Date.now() - initialTime;-  };-  requestHostCallback = function(cb) {-    if (_callback !== null) {-      // Protect against re-entrancy.-      setTimeout(requestHostCallback, 0, cb);-    } else {-      _callback = cb;-      setTimeout(_flushCallback, 0);-    }-  };-  cancelHostCallback = function() {-    _callback = null;-  };-  requestHostTimeout = function(cb, ms) {-    _timeoutID = setTimeout(cb, ms);-  };-  cancelHostTimeout = function() {-    clearTimeout(_timeoutID);-  };-  shouldYieldToHost = function() {-    return false;-  };-  requestPaint = forceFrameRate = function() {};+let getNow;+if (typeof perf === 'object' && typeof perf.now === 'function') {+  getNow = () => perf.now(); } else {-  // Capture local references to native APIs, in case a polyfill overrides them.-  const performance = window.performance;-  const Date = window.Date;-  const setTimeout = window.setTimeout;-  const clearTimeout = window.clearTimeout;+  const initialTime = date.now();+  getNow = () => date.now() - initialTime;+} -  if (typeof console !== 'undefined') {-    // TODO: Scheduler no longer requires these methods to be polyfilled. But-    // maybe we want to continue warning if they don't exist, to preserve the-    // option to rely on it in the future?-    const requestAnimationFrame = window.requestAnimationFrame;-    const cancelAnimationFrame = window.cancelAnimationFrame;-    // TODO: Remove fb.me link-    if (typeof requestAnimationFrame !== 'function') {-      // Using console['error'] to evade Babel and ESLint-      console['error'](-        "This browser doesn't support requestAnimationFrame. " +-          'Make sure that you load a ' +-          'polyfill in older browsers. https://fb.me/react-polyfills',-      );-    }-    if (typeof cancelAnimationFrame !== 'function') {-      // Using console['error'] to evade Babel and ESLint-      console['error'](-        "This browser doesn't support cancelAnimationFrame. " +-          'Make sure that you load a ' +-          'polyfill in older browsers. https://fb.me/react-polyfills',-      );-    }+let isMessageLoopRunning = false;+let scheduledHostCallback = null;+let taskTimeoutID = -1;++// Scheduler periodically yields in case there is other work on the main+// thread, like user events. By default, it yields multiple times per frame.+// It does not attempt to align with frame boundaries, since most tasks don't+// need to be frame aligned; for those that do, use requestAnimationFrame.+let yieldInterval = 5;+let deadline = 0;++// `isInputPending` is not available. Since we have no way of knowing if+// there's pending input, always yield at the end of the frame.+export const shouldYieldToHost = function() {+  return getNow() >= deadline;+};++// Since we yield every frame regardless, `requestPaint` has no effect.+export const requestPaint = function() {};++export const forceFrameRate = function(fps) {+  if (fps < 0 || fps > 125) {+    // Using console['error'] to evade Babel and ESLint+    console['error'](+      'forceFrameRate takes a positive int between 0 and 125, ' ++        'forcing frame rates higher than 125 fps is not unsupported',

not unsupported

😀

rickhanlonii

comment created time in 2 months

issue closedfacebook/react

Bug: Passing valid and then empty style value doesn't remove prior value

React version: 16.13.1

Steps To Reproduce

  1. Give element a valid backgroundColor: style={{backgroundColor: 'blue'}}
  2. Update component so that on the next render you have a commented-out value: style={{backgroundColor: '/*blue*/'}}, or any value deemed "invalid" by React.

Link to code example:

A code sandbox that toggles with the two above examples, and a toggle on click is provided here: https://codesandbox.io/s/adoring-currying-z4x2r?file=/src/App.tsx:316-320

The current behavior

If I pass a valid string to an element's style property, e.g. style={{border: '20px solid rebeccapurple'}}, and then update that value to e.g., 'nonsense', the new invalid value is not pushed to the DOM. However the old value is kept on the DOM.

Furthermore, updating a valid value, e.g. style={{backgroundColor: 'blue'}} with a valid empty value, e.g. style={{backgroundColor: '/*blue*/'}} does the same: the old value is kept on the DOM.

The expected behavior

An invalid value or an empty valid value would at least either remove the previous value from the DOM, or be pushed through. (I've not understood why invalid values weren't pushed through and am genuinely curious to hear if there is a good reason, would love to learn.)

closed time in 2 months

alecmolloy

issue commentfacebook/react

Bug: Passing valid and then empty style value doesn't remove prior value

Hey @alecmolloy, this is expected behavior and not something controlled by React. Here's an example showing the same thing with just the DOM APIs. If you set a style property to an invalid value the DOM will just ignore it.

Furthermore, updating a valid value, e.g. style={{backgroundColor: 'blue'}} with a valid empty value, e.g. style={{backgroundColor: '/blue/'}} does the same: the old value is kept on the DOM.

Values like "/*blue*/" aren't considered empty. The DOM APIs don't understand that those are meant to be commented out values, it just sees a string with some content. Something like <div style="background-color: /* blue */"> does work in HTML, but React's JSX compiles to JavaScript not HTML so it's one of the nuanced differences.

If you want to unset a value you can use "" or null. Hope that helps!

alecmolloy

comment created time in 2 months

issue commentfacebook/react

Bug: useContext out of the box (from docs example) is not working as expected

@cemceliks you're importing ThemeContext from your App.js file, which is exporting a component not a context. You need to pass the context you created here to useContext. Maybe move that into a ThemeContext.js file and have other modules import from there?

For future reference we try to use this issue tracker for bug reports and feature requests only. If you have more trouble I recommend checking out the list of great support resources listed on the doc page, Where to Get Support.

cemceliks

comment created time in 2 months

issue closedfacebook/react

Bug: useContext out of the box (from docs example) is not working as expected

Hi, I have actually finished this site with no other commits yet on GitHub. During refactoring wanted to use Context for various aspects but could not make it work on the project during refactoring. So I set up a totally new project and only used the example from the reference from React docs website as stated below on Step 1. Website is built with hooks and function components only.

package.json info "@u-wave/react-vimeo": "^0.9.0", "react": "^16.13.1", "react-dom": "^16.13.1", "react-scripts": "3.4.1"

Totally new project with no extra dependencies and no other installation than Vimeo player at the moment, which is not yet used anywhere. No other files in the project other than the 3 components mentioned to create the useContext example.

React version: Versions above

Steps To Reproduce

  1. From reference on documentation page https://reactjs.org/docs/hooks-reference.html for useContext
  2. Have 3 components as per the example there namely App.js, Toolbar.js and ThemedButton.js
  3. I have my imports where needed and useContext imports where needed. No issues with compilation and all code seem to be clean after nom start.

Link to code example: https://github.com/cemceliks/watson Committed as "useContext example". The only commit there so far.

The current behavior

Errors on Google Chrome render on npm start and errors on google dev tools Console. Error: Cannot read property of "background" of undefined in ThemedButton.js

The expected behavior

useContext to be able to access the values set by the Context object with its provider.

closed time in 2 months

cemceliks

startedjamiebuilds/tinykeys

started time in 2 months

startedandroidx/androidx

started time in 2 months

issue closedaweary/twitter-required-alt-text

Tweeting is not blocked on quote tweets with an image

If you quote tweet and add an image, the extension does not force you to add alt-text.

image

closed time in 2 months

bnb

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha f8647a36bf5deb965b07ff1cdc3de0fd725b37ba

Prevent tweet keyboard shortcut for propagating when labels are missing

view details

Brandon Dail

commit sha 0cc60c90a12b109ac8af6081f6bdd237978fe5ce

Merge pull request #7 from aweary/fix-enter-shortcut Prevent tweet keyboard shortcut for propagating when labels are missing

view details

push time in 2 months

issue closedaweary/twitter-required-alt-text

Keyboard shortcut to send tweet is not disabled when alt text is missing

currently if you command/control + enter while alt text is missing, a tweet will be sent.

OS: macOSS Browser: Edge (Canary) Views: Modal and inline tweet (maybe reply, too)

closed time in 2 months

bnb

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha f8647a36bf5deb965b07ff1cdc3de0fd725b37ba

Prevent tweet keyboard shortcut for propagating when labels are missing

view details

push time in 2 months

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha eb246290fedc405cef0ed69f61903b41966035ee

Prevent tweet keyboard shortcut for propagating when labels are missing

view details

push time in 2 months

create barnchaweary/twitter-required-alt-text

branch : fix-enter-shortcut

created branch time in 2 months

issue commentaweary/twitter-required-alt-text

Keyboard shortcut to send tweet is not disabled when alt text is missing

Nice, I didn't know about this shortcut! Maybe we can add an event listener for keydown and prevent it from propagating. I'll look into it.

bnb

comment created time in 2 months

issue closedfacebook/react

React is not offering suggestions/guideline for managing environment specific configuration

When building application we often have to deploy in multiple environments such as dev, staging and production. Some times instead of one production we might prod-cust1, prod-cust2, etc...

React is NOT offering any suggestions or guidelines how to manage environment specific configuration file. Angular is offering this suggestion https://angular.io/guide/build The suggestion offered by Angular is less than optimal. Many developers are adopting an approach similar to Angular approach for configurations

The problems in Angular approach

  • The code and the configuration is not separated (this is against the guideline of 12 factor app)
  • It also doesn't help Build Once Deploy Anywhere

It would be optimal if React suggests a way to separate configuration and code There are many ways in which the config and code could be separated. Two ways are interesting

  1. Have the configuration in the public folder and add it as script in index.html Have a file named Config.js that exports config by assessing window.config

  2. Have a mechanism to get the config from the backend on start up

React could choose option 1 as the default mechanism and the user could change it option 2

Suggestion change:

  1. Modify create-react-app so that configuration is separated from code as suggested in option 1
  2. Have a parameter in create-react-app so that the use could choose option 2

Also to consider: create-react-app based on a parameter provides a Dockerfile and .docekerignore

closed time in 2 months

nachiappannk

issue commentfacebook/react

React is not offering suggestions/guideline for managing environment specific configuration

Hey @nachiappannk! As a library React does not have any opinions on how to approach environmental variables or deployment (outside of using production builds. If you have suggestions or ideas on how Create React App should handle this, please direct those to the create-react-app repo which is maintained as a separate project.

Thanks!

nachiappannk

comment created time in 2 months

PR closed facebook/react

Update PULL_REQUEST_TEMPLATE.md CLA Signed

added more detailed steps

<!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

Before submitting a pull request, please make sure the following is done:

  1. Fork the repository and create your branch from master.
  2. Run yarn in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (yarn test). Tip: yarn test --watch TestName is helpful in development.
  5. Run yarn test-prod to test in the production environment. It supports the same options as yarn test.
  6. If you need a debugger, run yarn debug-test --watch TestName, open chrome://inspect, and press "Inspect".
  7. Format your code with prettier (yarn prettier).
  8. Make sure your code lints (yarn lint). Tip: yarn linc to only check changed files.
  9. Run the Flow type checks (yarn flow).
  10. If you haven't already, complete the CLA.

Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html -->

Summary

<!-- Explain the motivation for making this change. What existing problem does the pull request solve? -->

Test Plan

<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. -->

+35 -20

4 comments

1 changed file

ShreyPatel4

pr closed time in 2 months

pull request commentfacebook/react

Update PULL_REQUEST_TEMPLATE.md

Thanks, but I think we'll stick with what we have!

ShreyPatel4

comment created time in 2 months

PR closed facebook/react

0.4 stable

<!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

Before submitting a pull request, please make sure the following is done:

  1. Fork the repository and create your branch from master.
  2. Run yarn in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (yarn test). Tip: yarn test --watch TestName is helpful in development.
  5. Run yarn test-prod to test in the production environment. It supports the same options as yarn test.
  6. If you need a debugger, run yarn debug-test --watch TestName, open chrome://inspect, and press "Inspect".
  7. Format your code with prettier (yarn prettier).
  8. Make sure your code lints (yarn lint). Tip: yarn linc to only check changed files.
  9. Run the Flow type checks (yarn flow).
  10. If you haven't already, complete the CLA.

Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html -->

Summary

<!-- Explain the motivation for making this change. What existing problem does the pull request solve? -->

Test Plan

<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. -->

+1350 -288

1 comment

63 changed files

alantranhs

pr closed time in 2 months

issue commentaweary/twitter-required-alt-text

Tweeting is not blocked on quote tweets with an image

@bnb does this consistently not work in the PWA version? I didn't test it in the PWA version, I'll have to look into that.

bnb

comment created time in 2 months

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha c635249d8c78ce0789bf5a6f3bafbeb9b2776e00

v1.1

view details

push time in 2 months

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha bf4d5285d7d5229d2fe4d593e48809c1788145d7

v1.1

view details

push time in 2 months

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha e8a148bc0dc6441ab8fe3ee53c634ef9fa50f2c0

Require alt text for GIFs too

view details

Brandon Dail

commit sha b36da5f4e3247b4800e03e2cad7395a7e6b35a05

Merge pull request #5 from aweary/fix-gif-alt Require alt text for GIFs

view details

push time in 2 months

issue closedaweary/twitter-required-alt-text

Does not block tweeting for GIFs without alt descriptions

Seems that GIFs are not blocked from being tweeted without an alt.

image

closed time in 2 months

bnb

issue commentaweary/twitter-required-alt-text

Does not block tweeting for GIFs without alt descriptions

Should be fixed by https://github.com/aweary/twitter-required-alt-text/pull/5

bnb

comment created time in 2 months

PR opened aweary/twitter-required-alt-text

Require alt text for GIFs

Resolves #4

+11 -23

0 comment

3 changed files

pr created time in 2 months

create barnchaweary/twitter-required-alt-text

branch : fix-gif-alt

created branch time in 2 months

issue commentaweary/twitter-required-alt-text

Does not block tweeting for GIFs without alt descriptions

For some reason I thought you couldn't add alt text to GIFs, I must have missed that! I intentionally excluded them, so this actually simplifies things.

bnb

comment created time in 2 months

issue commentaweary/twitter-required-alt-text

Tweeting is not blocked on quote tweets with an image

Tracking that issue here: https://github.com/aweary/twitter-required-alt-text/issues/3

bnb

comment created time in 2 months

issue openedaweary/twitter-required-alt-text

Does not block tweets in the "Tweet" modal if you are also composing a tweet in the inline composition input above the newsfeed

Steps to Reproduce

  • Open Twitter
  • Start a tweet from the inline composition input, add an image
  • Click the Tweet button in the left column
  • Start composing a new tweet with an image

Notice that it won't disable the Tweet button in this modal. I think we just need to disable all instances of the Tweet button, rather than the first one (i.e., change querySelector to querySelectorAll and iterate through every button)

created time in 2 months

issue commentaweary/twitter-required-alt-text

Tweeting is not blocked on quote tweets with an image

Did you perhaps have a Tweet composed in the main composition interface? I think if there are two active compositions it can end up disabling the one outside the modal, making it look like it's not doing anything.

bnb

comment created time in 2 months

issue commentaweary/twitter-required-alt-text

Tweeting is not blocked on quote tweets with an image

Interesting, I can't reproduce that! Are you getting any errors in the console?

image

bnb

comment created time in 2 months

issue closedaweary/twitter-required-alt-text

Button text gets reset if a tweet gets scheduled

If you add an image and then attempt to schedule the tweet for later the button will change text to "Schedule". We want it to say "Add Alt Text" no matter what and have it reset back to whatever it would be once that's done.

Maybe we can use CSS to override the text instead?

closed time in 2 months

aweary

issue commentaweary/twitter-required-alt-text

Button text gets reset if a tweet gets scheduled

This one is fixed now

aweary

comment created time in 2 months

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha b924d49385b8a506df96809587137839acbaf94b

Rewrite in TypeScript, update permissions

view details

push time in 2 months

pull request commentfacebook/prop-types

doc: highlighted the func name

Thanks!

mhkasif

comment created time in 2 months

push eventfacebook/prop-types

Haseeb Khan

commit sha 8f89a1cde81f2a32f3295795b037499afa900d3b

doc: highlighted the func name (#321)

view details

push time in 2 months

PR merged facebook/prop-types

doc: highlighted the func name CLA Signed
+1 -1

0 comment

1 changed file

mhkasif

pr closed time in 2 months

startedjamiebuilds/babel-plugin-hash-strings

started time in 2 months

push eventaweary/twitter-required-alt-text

Brandon Dail

commit sha beda5dc994c94a52d6a124caf69e3fb8bc3b1ef0

don't crash if findTextNode is passed null

view details

push time in 2 months

issue openedaweary/twitter-required-alt-text

Button text gets reset if a tweet gets scheduled

If you add an image and then attempt to schedule the tweet for later the button will change text to "Schedule". We want it to say "Add Alt Text" no matter what and have it reset back to whatever it would be once that's done.

Maybe we can use CSS to override the text instead?

created time in 2 months

more