This is available in the v1.0.0-beta.17 releases

Problem

#210

We need a method to check if a build exists, in order to avoid e.g. re-uploading builds for comparison in CI jobs. If a build has already been uploaded, no need to do so again. This will also avoid issues relating to duplicate primary keys when rebuilding.

Solution

This is totally WIP but here I'm adding a method that should simply call through to the server:read method for checking builds.

TODO

• [x] 🤓 Add & update tests (always try to increase test coverage)
• [x] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [ ] 📖 Update relevant documentation
• [x] 🕵️‍♀️ Check relevant internals are being called by method
• [x] 💻 Update CLI to include get-build method

<!-- Thank you so much for contributing to open source and the Build Tracker project! -->

Problem

Docs aren't building on Node 12

Solution

• Upgrade docusaurus
  • Requires nohoist on html-minifier-terser due to https://github.com/facebook/docusaurus/issues/3515#issuecomment-707145367
• Fix broken links
• Change github action to be simpler

TODO

• [ ] 🤓 Add & update tests (always try to increase test coverage)
• [x] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [x] 📖 Update relevant documentation

<!-- Thank you so much for contributing to open source and the Build Tracker project! -->

Problem

Docs aren't building on Node 12

Solution

Upgrade docusaurus, fix actions

TODO

• [ ] 🤓 Add & update tests (always try to increase test coverage)
• [ ] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [ ] 📖 Update relevant documentation

<!-- Thank you so much for contributing to open source and the Build Tracker project! -->

Problem

Switching from Node 10 to Node 12 produces an issue that suddenly brotli will be included in available sizeKeys for builds. This causes various things to throw errors because they're hardcoded to not allow a change in the sizeKeys

Solution

This manual throwing seems unnecessary. By removing these checks, we can allow comparisons with the given keys, the result will just cause the comparison to show 0s for the build missing that size key.

Also updated CI to node 12

TODO

• [x] 🤓 Add & update tests (always try to increase test coverage)
• [x] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [x] 📖 Update relevant documentation

<!-- Thank you so much for contributing to open source and the Build Tracker project! -->

Problem

Some people use really long git branch names, sometimes automated systems do that. We currently limit branch names in the official database plugins to 64 characters.

Solution

Increase to 256 characters.

Fixes #205

Ideally in a longer term solution, we should include schema versions in the database to know what migrations need to be run. This is something we could investigate as a larger epic.

TODO

• [x] Manual verification with docker containers: https://buildtracker.dev/docs/guides/contributing#plugins-plugins
• [x] 🤓 Add & update tests (always try to increase test coverage)
• [x] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [x] 📖 Update relevant documentation

<!--

IMPORTANT! Follow the format of this template or your issue will be automatically closed by a bot. Following this template helps keep the quality of bug reports high, which will help them be addressed sooner.

-->

Problem

<!-- Add a short explanation of your problem or use-case

Example: When I click the drawer link, nothing happens! -->

Steps to Reproduce

<!-- Include a list of steps that anyone can take to reproduce the bug If you have a code sample, this is a great place to include it

Example:

1. Navigate to the main Build Tracker page
2. Click the menu button to open the side drawer
3. Click "Documentation" link -->

New issue because https://github.com/paularmstrong/build-tracker/issues/203 was automatically closed

The database setup defines a branch as max 64 characters. Just today we had a build fail because we actually ran into this limit (not a branch name we defined ourselves, but one created by GitHub's "revert PR" functionality).

Could we increase the max length?

Expected Result

<!-- Write out what you expect to see or have happen when running the previous steps

Example: The link should open a new page to the documentation -->

Actual Result

<!-- Write out what actually happens when running the previous steps

Example: Nothing happens. But I do see an error in the browser's console. It looks like this:

TypeError: cannot read property href of undefined -->

<!--

IMPORTANT! Follow the format of this template or your issue will be automatically closed by a bot. Following this template helps keep the quality of feature requests high, which will help them be addressed sooner.

-->

Problem

The database plugins are setup with setting revision key as the PRIMARY_KEY. However if we re-run the build tracker job it ends up in a duplicate key error ( Since the sha is the same).

<!-- Explain the problem you'd like to have Build Tracker solve. When trying to solve more solutions with Build Tracker, please keep in mind some of the following goals of the project:

• Be lightweight: small project size (single-digit KiBs, gzipped)
• Be easy: too many options in an API can become confusing
• Be clear: the intended purpose of every method should be obvious
• Is it easy to do this in "userland"? Would it be better off done there? -->

Proposed solution

I'm proposing adding a unique ID key to each row which will have the property of Uniq and Primary Key. This way subsequent re-runs will ensure that the job works even the sha is unchanges. <!-- Explain a possible way to solve the problem. Keep in mind that there may be alternate ways to do the same thing. Try to think of those and weight the tradeoffs. -->

Discussed in person. We'll be implementing a getBuild() method in the @build-tracker/api-client to allow checking for existing builds to avoid attempting to double-post.

<!-- Thank you so much for contributing to open source and the Build Tracker project! -->

Problem

Switching from Node 10 to Node 12 produces an issue that suddenly brotli will be included in available sizeKeys for builds. This causes various things to throw errors because they're hardcoded to not allow a change in the sizeKeys

Solution

This manual throwing seems unnecessary. By removing these checks, we can allow comparisons with the given keys, the result will just cause the comparison to show 0s for the build missing that size key.

TODO

• [ ] 🤓 Add & update tests (always try to increase test coverage)
• [ ] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [ ] 📖 Update relevant documentation

Bumps node-fetch from 2.6.0 to 2.6.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bitinn/node-fetch/releases">node-fetch's releases</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <p>See <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261">CHANGELOG</a> for details.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md">node-fetch's changelog</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <ul> <li>Fix: honor the <code>size</code> option after following a redirect.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab"><code>b5e2e41</code></a> update version number</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334"><code>2358a6c</code></a> Honor the <code>size</code> option after following a redirect and revert data uri support</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4"><code>8c197f8</code></a> docs: Fix typos and grammatical errors in README.md (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/686">#686</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1e99050f944ac435fce26a9549eadcc2419a968a"><code>1e99050</code></a> fix: Change error message thrown with redirect mode set to error (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/653">#653</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/244e6f63d42025465796e3ca4ce813bf2c31fc5b"><code>244e6f6</code></a> docs: Show backers in README</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/6a5d192034a0f438551dffb6d2d8df2c00921d16"><code>6a5d192</code></a> fix: Properly parse meta tag when parameters are reversed (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/682">#682</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/47a24a03eb49a49d81b768892aee10074ed54a91"><code>47a24a0</code></a> chore: Add opencollective badge</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/7b136627c537cb24430b0310638c9177a85acee1"><code>7b13662</code></a> chore: Add funding link</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/5535c2ed478d418969ecfd60c16453462de2a53f"><code>5535c2e</code></a> fix: Check for global.fetch before binding it (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/674">#674</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1d5778ad0d910dbd1584fb407a186f5a0bc1ea22"><code>1d5778a</code></a> docs: Add Discord badge</li> <li>Additional commits viewable in <a href="https://github.com/bitinn/node-fetch/compare/v2.6.0...v2.6.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/~akepinski">akepinski</a>, a new releaser for node-fetch since your current version.</p> </details> <br />

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>

<!-- Thank you so much for contributing to open source and the Build Tracker project! -->

Problem

Some people use really long git branch names, sometimes automated systems do that. We currently limit branch names in the official database plugins to 64 characters.

Solution

Increase to 256 characters.

Fixes #205

Ideally in a longer term solution, we should include schema versions in the database to know what migrations need to be run. This is something we could investigate as a larger epic.

TODO

• [ ] Manual verification with docker containers: https://buildtracker.dev/docs/guides/contributing#plugins-plugins
• [x] 🤓 Add & update tests (always try to increase test coverage)
• [ ] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [x] 📖 Update relevant documentation

<!-- Thank you so much for contributing to open source and the Normalizr project! -->

Problem

This lock file is a source of dependency/security issues that we don't really need to deal with

Solution

delete. also delete greenkeeper config, since we don't use it

TODO

• [ ] Add & update tests
• [ ] Ensure CI is passing (lint, tests, flow)
• [ ] Update relevant documentation

<!-- Thank you so much for contributing to open source and the Normalizr project! -->

Problem

This lock file is a source of dependency/security issues that we don't really need to deal with

Solution

delete. also delete greenkeeper config, since we don't use it

TODO

• [ ] Add & update tests
• [ ] Ensure CI is passing (lint, tests, flow)
• [ ] Update relevant documentation

<!-- Thank you so much for contributing to open source and the Normalizr project! -->

Problem

Lots of outdated development dependencies.

Solution

Upgrade them

TODO

• [x] Add & update tests
• [x] Ensure CI is passing (lint, tests, flow)
• [x] Update relevant documentation

Thanks @paulirish !

Problem

Problem

Sometimes buildtracker fails randomly. Example: https://github.com/GoogleChrome/lighthouse/runs/1130093961?check_suite_focus=true#step:19:25

since we have no idea what command triggered a nonzero exit code, it's a bit hard to debug.

Solution

since the error object that spawn() rejects with already has a few things, and is logged out to stderr... i figure why not.

fixes #200

TODO

• [X] 🤓 Add & update tests (always try to increase test coverage)
• [x] 🔬 Ensure CI is passing (yarn lint:ci, yarn test, yarn tsc:ci)
• [X] 📖 Update relevant documentation

Problem

Sometimes buildtracker fails randomly. Example: https://github.com/GoogleChrome/lighthouse/runs/1130093961?check_suite_focus=true#step:19:27

We saw errors like this before: https://github.com/paularmstrong/build-tracker/issues/195 Although that time there was a more useful stderr to read.

feature request: If -v is on, i'd love to enable something like this at the top of spawn.ts:

console.log('running', `${command} ${args.join(' ')}`);

I obviously considered writing this myself, but am not entirely sure how you want to carry the args that deep.

Steps to Reproduce

The first link above's failure is completely intermittent. No idea how to reproduce.

Expected Result

Of course, no bugs. But I figure some better debug logging would help isolate whatever problem is going on.

Actual Result

An error without any useful info.

Bumps lodash from 4.17.14 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.14...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 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>

<!-- Thank you so much for contributing to open source and the Normalizr project! -->

Problem

Lots of outdated development dependencies.

Solution

Upgrade them

TODO

• [x] Add & update tests
• [x] Ensure CI is passing (lint, tests, flow)
• [x] Update relevant documentation

<!-- Thank you so much for contributing to open source and the Normalizr project! -->

Problem

It's just confuse to having the same property sometimes to be Id, sometimes to be an object/array. And that problem is particularly annoying when it comes to using TypeScript, as user have to define the type either like user: number|User or user: any.

Found one issue on this one. https://github.com/paularmstrong/normalizr/issues/423

Solution

Add an optional option to suffixed id to the property.

      const user = new schema.Entity('users', {}, { keyNamingStrategy: 'camelCase' });
      const comment = new schema.Entity('comments', {}, { keyNamingStrategy: 'camelCase' });
      const article = new schema.Entity(
        'articles',
        {
          author: user,
          comments: [comment]
        },
        { keyNamingStrategy: 'camelCase' }
      );

      const input = {
        id: '123',
        title: 'A Great Article',
        author: {
          id: '8472',
          name: 'Paul'
        },
        body: 'This article is great.',
        comments: [
          {
            id: 'comment-123-4738',
            comment: 'I like it!'
          }
        ]
      };

result

"entities": Object {
    "articles": Object {
      "123": Object {
        "authorId": "8472",
        "body": "This article is great.",
        "commentsIds": Array [
          "comment-123-4738",
        ],
        "id": "123",
        "title": "A Great Article",
      },
    },
    "comments": Object {
      "comment-123-4738": Object {
        "comment": "I like it!",
        "id": "comment-123-4738",
      },
    },
    "users": Object {
      "8472": Object {
        "id": "8472",
        "name": "Paul",
      },
    },
  },
  "result": "123",

TODO

• [x] Add & update tests
• [x] Ensure CI is passing (lint, tests, flow)
• [ ] Update relevant documentation

As noted in the issue that you linked, this is a major change that would be better off in a fork of normalizr.

fix #427

Problem

Project in examples/redux does not run #427

Babel was updated to 7. Refs #377, #318

I think it's necessary to upgrade babel in examples too.

Solution

This is work in progress right now.

I just upgraded modules and copied babel configs.

But it’s still has an issue with module importing.

➜  redux git:(master) ✗ yarn start
yarn run v1.19.2
$ babel-node ./
/PATH/TO/normalizr/src/index.js:1
import * as ImmutableUtils from './schemas/ImmutableUtils';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Module._compile (internal/modules/cjs/loader.js:895:18)

TODO

• [ ] Fix import problem described in above.
• [ ] Add & update tests
• [ ] Ensure CI is passing (lint, tests)
• [ ] Update relevant documentation

Maybe it's nice to check validity of code in examples using CI.

Bumps qs from 6.3.0 to 6.3.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ljharb/qs/blob/master/CHANGELOG.md">qs's changelog</a>.</em></p> <blockquote> <h2><strong>6.3.2</strong></h2> <ul> <li>[Fix] follow <code>allowPrototypes</code> option during merge (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/201">#201</a>, <a href="https://github-redirect.dependabot.com/ljharb/qs/issues/200">#200</a>)</li> <li>[Dev Deps] update <code>eslint</code></li> <li>[Fix] chmod a-x</li> <li>[Fix] support keys starting with brackets (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/202">#202</a>, <a href="https://github-redirect.dependabot.com/ljharb/qs/issues/200">#200</a>)</li> <li>[Tests] up to <code>node</code> <code>v7.7</code>, <code>v6.10</code>,<code> v4.8</code>; disable osx builds since they block linux builds</li> </ul> <h2><strong>6.3.1</strong></h2> <ul> <li>[Fix] ensure that <code>allowPrototypes: false</code> does not ever shadow Object.prototype properties (thanks, <a href="https://github.com/snyk">@snyk</a>!)</li> <li>[Dev Deps] update <code>eslint</code>, <code>@ljharb/eslint-config</code>, <code>browserify</code>, <code>iconv-lite</code>, <code>qs-iconv</code>, <code>tape</code></li> <li>[Tests] on all node minors; improve test matrix</li> <li>[Docs] document stringify option <code>allowDots</code> (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/195">#195</a>)</li> <li>[Docs] add empty object and array values example (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/195">#195</a>)</li> <li>[Docs] Fix minor inconsistency/typo (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/192">#192</a>)</li> <li>[Docs] document stringify option <code>sort</code> (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/191">#191</a>)</li> <li>[Refactor] <code>stringify</code>: throw faster with an invalid encoder</li> <li>[Refactor] remove unnecessary escapes (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/184">#184</a>)</li> <li>Remove contributing.md, since <code>qs</code> is no longer part of <code>hapi</code> (<a href="https://github-redirect.dependabot.com/ljharb/qs/issues/183">#183</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ljharb/qs/commit/9ee56121311dac6b6014bfe56b3df0ebbf4ed048"><code>9ee5612</code></a> v6.3.2</li> <li><a href="https://github.com/ljharb/qs/commit/0a63fc8686bcc89d939522913762d1c6b1c4faa5"><code>0a63fc8</code></a> [Tests] up to <code>node</code> <code>v7.7</code>, <code>v6.10</code>,<code> v4.8</code>; disable osx builds since they b...</li> <li><a href="https://github.com/ljharb/qs/commit/8e1f3e743e81df157ccffea20b461ab6e499a795"><code>8e1f3e7</code></a> [Fix] support keys starting with brackets.</li> <li><a href="https://github.com/ljharb/qs/commit/febe81ad7e9120fab8db1897ec98c92297249a7c"><code>febe81a</code></a> [Fix] chmod a-x</li> <li><a href="https://github.com/ljharb/qs/commit/e54c5ec8e20e3beacddff4d775d1a29bcaa47dc1"><code>e54c5ec</code></a> [Dev Deps] update <code>eslint</code></li> <li><a href="https://github.com/ljharb/qs/commit/8e2af085b448eeb0b8068f4c7828e6a68c910058"><code>8e2af08</code></a> [Fix] follow <code>allowPrototypes</code> option during merge</li> <li><a href="https://github.com/ljharb/qs/commit/153ce84948845330d90178cbad982fc7371df538"><code>153ce84</code></a> v6.3.1</li> <li><a href="https://github.com/ljharb/qs/commit/d73b7a6cb2f0b2cfb0e73a6aeefde8cdcb521a98"><code>d73b7a6</code></a> [Dev Deps] update <code>eslint</code>, <code>@ljharb/eslint-config</code>, <code>browserify</code></li> <li><a href="https://github.com/ljharb/qs/commit/beade029171b8cef9cee0d03ebe577e2dd84976d"><code>beade02</code></a> [Fix] ensure that <code>allowPrototypes: false</code> does not ever shadow Object.protot...</li> <li><a href="https://github.com/ljharb/qs/commit/8bd4c6cf12898f469838980317fec92007e5112a"><code>8bd4c6c</code></a> Document allowDots option for stringify</li> <li>Additional commits viewable in <a href="https://github.com/ljharb/qs/compare/v6.3.0...v6.3.2">compare view</a></li> </ul> </details> <br />

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>

Happaned again. Found a sample Sample of Home Assistant.txt

Okay, it's doing it again. I was clicking around between views in the dashboard and after one showed it suddenly froze.

No beachball in the app. Activity monitor looks fine

I see a lot of this in the Console

Of course it cleared up after the app was closed for a few hours then reopened. I'll check when/if it happens again.

+1 approval, including clarification of week leading up to and of election @mrjoro Could you amend this as start and end date for clarity?

<!-- Please READ THIS FIRST If your issue relates to something not looking right on Home Assistant within the Companion App, please check if the error is present in Safari on macOS too. If the issue is also seen in Safari, please open an issue on the frontend repo (https://github.com/home-assistant/frontend/issues/new?labels=bug&template=BUG_REPORT.md) instead -->

Device model, version and app version <!-- Please include your mac's model and version as listed in 'About This Mac'. Please also give the app version listed in the Home Assistant>About Home Assistant, please include the number in brackets -->

Model Name: MacBookPro 13-inch 2020 Software Version: OS X 10.15.6 App version: 2020.7 (2)

Home Assistant Core Version 0.115.2

Describe the bug The app does not respond to any click/mouse/keyboard input. System menus work fine, but nothing in the UI will respond. Accessing the same HA installation from a web browser works fine.

To Reproduce Unknown, but mine is stuck in this state, even after quit and re-open.

Expected behavior It does not become unresponsive

Screenshots N/A <!-- If applicable, add screenshots to help explain your problem. -->

Additional context <!--Add any other context about the problem here.-->

 const nodeArraySchema = new schema.Array(nodeSchema)

 nodeArraySchema.key ---> 'nodes'

Problem

In blog post, the user entity not used in sample JSON, however used in the normalizr code example

Solution

The user entity is changed to author for more clarity

TODO

• [ ] Update relevant documentation

@luccamordente is right, the original example is correct as both author and commenter are both the same user entity, just attached to different objects

unstable_createElement already does what you're asking for. You're just going a hugely roundabout and unnecessary way. Here's an example SVG that I have: https://github.com/paularmstrong/build-tracker/blob/master/src/app/src/icons/ArrowLeft.tsx You don't need to set innerHtml or any of the extra stuff.

Just saw #44

@googlebot I signed it!

flow-copy-source or DIY copy every file over to your dist directory and add .flow as the final extension. Probably also need to ensure // @flow is at the top of every file that supports types

Ah, they're not exporting types, correct. I believe I had done something with the module.name_mapper to re-map to the src files. It worked out okay, but not everything was fully typed at the time. And the main index.js not having // @flow at the top was problematic as well.

I'm not as connected with that area of our code anymore, so I'm not certain what we have that's more strict. Maybe @comp615 has some thoughts on that.

The one thing that I've noticed that's really nice about the TypeScript types from react-native that I'm using in Build Tracker is that the StyleSheet props are fully typed and throws errors if you use a style that isn't allowed (like color on a View doesn't work, but will on Text). We definitely don't have that same level of strict typing in Flow.

In Build Tracker (typescript, web-only), I pulled the react-native types from definitely-typed, then removed all of the iOS/Android specific stuff and added web-specific bits. Ideally I would take the few minutes to contribute this back, but I don't feel comfortable enough with my knowledge on Typescript to really be authoritative that any of it was done correctly.

At Twitter, we have our own flow definitions for react-native-web, but had built this up before this package was exporting most of its types. Ideally, we would love to use the source here, but have found that our type definitions tend to be more strict (which we like).

Maybe instead of closing this so quickly, we could have it added to the setup instructions?