Skip to content

build(deps-dev): bump @open-wc/testing from 3.0.0-next.3 to 3.0.0-next.5 - #476

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/open-wc/testing-3.0.0-next.5
Open

build(deps-dev): bump @open-wc/testing from 3.0.0-next.3 to 3.0.0-next.5#476
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/open-wc/testing-3.0.0-next.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 4, 2021

Copy link
Copy Markdown
Contributor

Bumps @open-wc/testing from 3.0.0-next.3 to 3.0.0-next.5.

Release notes

Sourced from @​open-wc/testing's releases.

@​open-wc/testing@​3.0.0-next.5

Minor Changes

  • 22c4017c: Undo deprecation of the html and unsafeStatic exports to enable matching lit versions to what is used in fixture.

    A typical testing file looks like this

    import { html, fixture } from '@open-wc/testing'; // html will be lit-html 2.x
    it('works for tags', async () => {
    const el = await fixture(
    html<my-el></my-el>,
    );
    });

    With this export you can combine the usage of lit-html 2.x for the fixture and template rendering in lit-html 1.x

    import { html as fixtureHtml, fixture } from '@open-wc/testing'; // fixtureHtml will be lit-html 2.x
    import { html } from 'my-library'; // html will be lit-html 1.x
    it('works for tags', async () => {
    const el = await fixture(fixtureHtml<my-el></my-el>);
    });
    it('can be combined', async () => {
    class MyExtension extends LibraryComponent {
    render() {
    // needs to be lit-html 1.x as the library component is using LitElement with lit-html 1.x
    return html<p>...</p>;
    }
    }
    // fixture requires a lit-html 2.x template
    const el = await fixture(fixtureHtml<my-el></my-el>);
    });

    NOTE: If you are using fixture for testing your lit-html 1.x directives then this will no longer work. A possible workaround for this is

    import { html, fixture } from '@open-wc/testing'; // html will be lit-html 2.x
    import { render, html as html1, fancyDirective } from 'my-library'; // html and render will be lit-html 1.x

... (truncated)

Changelog

Sourced from @​open-wc/testing's changelog.

3.0.0-next.5

Minor Changes

  • 22c4017c: Undo deprecation of the html and unsafeStatic exports to enable matching lit versions to what is used in fixture.

    A typical testing file looks like this

    import { html, fixture } from '@open-wc/testing'; // html will be lit-html 2.x
    it('works for tags', async () => {
    const el = await fixture(
    html<my-el></my-el>,
    );
    });

    With this export you can combine the usage of lit-html 2.x for the fixture and template rendering in lit-html 1.x

    import { html as fixtureHtml, fixture } from '@open-wc/testing'; // fixtureHtml will be lit-html 2.x
    import { html } from 'my-library'; // html will be lit-html 1.x
    it('works for tags', async () => {
    const el = await fixture(fixtureHtml<my-el></my-el>);
    });
    it('can be combined', async () => {
    class MyExtension extends LibraryComponent {
    render() {
    // needs to be lit-html 1.x as the library component is using LitElement with lit-html 1.x
    return html<p>...</p>;
    }
    }
    // fixture requires a lit-html 2.x template
    const el = await fixture(fixtureHtml<my-el></my-el>);
    });

    NOTE: If you are using fixture for testing your lit-html 1.x directives then this will no longer work. A possible workaround for this is

    import { html, fixture } from '@open-wc/testing'; // html will be lit-html 2.x

... (truncated)

Commits

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.


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)

Bumps [@open-wc/testing](https://github.com/open-wc/open-wc/tree/HEAD/packages/testing) from 3.0.0-next.3 to 3.0.0-next.5.
- [Release notes](https://github.com/open-wc/open-wc/releases)
- [Changelog](https://github.com/open-wc/open-wc/blob/master/packages/testing/CHANGELOG.md)
- [Commits](https://github.com/open-wc/open-wc/commits/@open-wc/testing@3.0.0-next.5/packages/testing)

---
updated-dependencies:
- dependency-name: "@open-wc/testing"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants