Bump @polymer/polymer from 3.3.1 to 3.4.0

[dependabot-preview]

Bumps @polymer/polymer from 3.3.1 to 3.4.0.

Release notes

Sourced from @polymer/polymer's releases.

v3.4.0

New global settings

This update to Polymer includes some new global settings:

• legacyUndefined / setLegacyUndefined

  What does it do? This setting reverts how computed properties handle undefined values to the Polymer 1 behavior: when enabled, computed properties will only be recomputed if none of their dependencies are undefined.

  Components can override the global setting by setting their _overrideLegacyUndefined property to true. This is useful for reenabling the default behavior as you migrate individual components:

  import {PolymerElement, html} from '@polymer/polymer/polymer-element.js';
  class MigratedElement extends PolymerElement { /* ... */ }
  // All MigratedElement instances will use the default behavior.
  MigratedElement.prototype._overrideLegacyUndefined = true;
  customElements.define('migrated-element', SomeElement);

  Should I use it? This setting should only be used for migrating legacy codebases that depend on this behavior and is otherwise not recommended.

• legacyWarnings / setLegacyWarnings

  What does it do? This setting causes Polymer to warn if a component's template contains bindings to properties that are not listed in that element's properties block. For example:

  import {PolymerElement, html} from '@polymer/polymer/polymer-element.js';
  class SomeElement extends PolymerElement {
    static get template() {
      return html`<span>[[someProperty]] is used here</span>`;
    }
    static get properties() {
      return { /* but `someProperty` is not declared here */ };
    }
  }
  customElements.define('some-element', SomeElement);

  Only properties explicitly declared in the properties block are associated with an attribute and update when that attribute changes. Enabling this setting will show you where you might have forgotten to declare properties.

  Should I use it? Consider using this feature during development but don't enable it in production.

• orderedComputed / setOrderedComputed

  What does it do? This setting causes Polymer to topologically sort each component's computed properties graph when the class is initialized and uses that order whenever computed properties are run.

  For example:

  import {PolymerElement, html} from '@polymer/polymer/polymer-element.js';

... (truncated)

Changelog

Sourced from @polymer/polymer's changelog.

v3.4.0 (2020-04-23)

New global settings

This update to Polymer includes some new global settings:

• legacyUndefined / setLegacyUndefined

  What does it do? This setting reverts how computed properties handle undefined values to the Polymer 1 behavior: when enabled, computed properties will only be recomputed if none of their dependencies are undefined.

  Components can override the global setting by setting their _overrideLegacyUndefined property to true. This is useful for reenabling the default behavior as you migrate individual components:

  import {PolymerElement, html} from '@polymer/polymer/polymer-element.js';
  class MigratedElement extends PolymerElement { /* ... */ }
  // All MigratedElement instances will use the default behavior.
  MigratedElement.prototype._overrideLegacyUndefined = true;
  customElements.define('migrated-element', SomeElement);

  Should I use it? This setting should only be used for migrating legacy codebases that depend on this behavior and is otherwise not recommended.

• legacyWarnings / setLegacyWarnings

  What does it do? This setting causes Polymer to warn if a component's template contains bindings to properties that are not listed in that element's properties block. For example:

  import {PolymerElement, html} from '@polymer/polymer/polymer-element.js';
  class SomeElement extends PolymerElement {
  static get template() {
  return html<span>[[someProperty]] is used here</span>;
  }
  static get properties() {
  return { /* but someProperty is not declared here */ };
  }
  }
  customElements.define('some-element', SomeElement);

  Only properties explicitly declared in the properties block are associated with an attribute and update when that attribute changes. Enabling this setting will show you where you might have forgotten to declare properties.

  Should I use it? Consider using this feature during development but don't enable it in production.

• orderedComputed / setOrderedComputed

... (truncated)

Commits

• 70ab725 3.4.0
• 0858531 [ci skip] bump to 3.4.0
• 2ce7163 Merge pull request #5497 from Polymer/legacy-undefined-noBatch
• 742a103 Merge pull request #5645 from Polymer/share-built-css-flag
• 33e1498 shareBuiltCSSWithAdoptedStyleSheets -> useAdoptedStyleSheetsWithBuiltCSS
• d0848d8 formatting
• c0813cd Fix incorrect JSDoc param name.
• bdd7658 Gate feature behind shareBuiltCSSWithAdoptedStyleSheets; update tests.
• 2fc9062 Add shareBuiltCSSWithAdoptedStyleSheets global setting
• 6cffb7b Merge pull request #5643 from Polymer/stalebot
• Additional commits viewable in compare view

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.

---

Dependabot commands and options

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
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[abraham]

Depends on Polymer/polymer#5651

[dependabot-preview]

Superseded by #942.