Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency html-validate to v8 #532

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
html-validate (source) ^7.0.0 -> ^8.0.0 age adoption passing confidence

Release Notes

html-validate/html-validate (html-validate)

v8.9.1

Compare Source

Bug Fixes
  • rules: <form> and <section> without explicit accessible name is no longer considered landmark (a36deac)
  • rules: <header> and <footer> nested in <main> or sectioning content is no longer considered landmark (bcab354), closes #​234

v8.9.0

Compare Source

Features
  • elements: new property focusable to mark elements as focusable (c59c8b2)
  • rules: new rule hidden-focusable (243e7fb)
  • rules: new rule unique-landmark (187be1e)
Bug Fixes
  • api: remove internal listeners property from public API (303e5d5)
  • dom: ancestor with role="presentation" no longer counts decendants as missing from a11y tree (cc72da1)
  • dom: handle role="none" as a synonym for role="presentation" (b1d7b50)
  • dom: interactive and focusable elements ignore role="presentation" (017308f)
  • rules: better error description for require-sri (ffc3695)
  • rules: rule wcag/h30 no longer requires text on <a hidden> (a20cc84)
  • rules: rule wcag/h30 no longer requires text on links with display: none or visibility: hidden (36ff07e)
  • rules: rules wcag/h32 handles <button> without explicit type (84c6a6e)

v8.8.0

Compare Source

Features
  • api: Report.merge() can merge async results (35689fc)
  • api: rename nodejsResolver to cjsResolver (8c72c8f)
  • config: new defineConfig helper (35e265a)
Bug Fixes
  • config: proper error message when certain configuration properties was invalid (b029569)

v8.7.4

Compare Source

Bug Fixes

v8.7.3

Compare Source

Bug Fixes
  • disable doctype-style when using prettier preset (f1f4004)

v8.7.2

Compare Source

Bug Fixes
  • deps: update dependency ignore to v5.3.0 (143e994)

v8.7.1

Compare Source

Bug Fixes
  • rules: fix form-dup-name issue when more than two names are present in array (5d9ff3b), closes #​228

v8.7.0

Compare Source

Features
  • html5: support referrerpolicy attribute (851b559)

v8.6.1

Compare Source

Bug Fixes
  • dom: remove usage of regex negative lookbehind (f406393), closes #​147
  • rules: improve attribute-misuse error message (fccce69), closes #​226
  • typo in CONTRIBUTING.md (855bacf)

v8.6.0

Compare Source

Features
  • api: add meta: MetaAttribute in AttributeEvent (2cda0ae)
  • cli: --rule severity can now be set with strings, fixes #​225. (054972e)

v8.5.0

Compare Source

Features

v8.4.1

Compare Source

Bug Fixes
  • rules: fix contextual documentation for attr-pattern rule (0082aef)

v8.4.0

Compare Source

Features
  • html5: support <search> element (720bdd9)
  • new implicitRole metadata for better handling of implicit ARIA roles (fe45ec4), closes #​224

v8.3.0

Compare Source

Features
Bug Fixes
  • html5: <label> cannot have empty for (3626e1a), closes #​223
  • html5: element-required-attributes allows <button> without type (use no-implicit-button-type instead) (d32f492), closes #​221

v8.2.0

Compare Source

Features
  • add allowedIfParentIsPresent metadata helper (2668899)
  • html5: add <source> attributes metadata (e3a3311)
  • support passing native HTMLElement to metadata helpers (8af6d01), closes #​207
Bug Fixes
  • api: typing for Rule.setSeverity() changed to only accept Severity (64f4210)

v8.1.0

Compare Source

Features
Bug Fixes
  • add compatibilityCheck function to browser bundle (b89dcc2)
  • api: remove unintended null return value from plugins api (0eb0ea8)

v8.0.5

Compare Source

Bug Fixes
  • fix import issue with elements/html5.js (0604c21), closes #​219
  • make elements/html5 work with esm (d95de27)

v8.0.4

Compare Source

Bug Fixes
  • add explicit node import (73f9a1f)

v8.0.3

Compare Source

Bug Fixes
  • fix regression bug when using elements in extended configuration files and plugins (6892083)
  • use correct dts when using custom conditions (1b6971e)

v8.0.2

Compare Source

Bug Fixes
  • add browser condition for main import (d2f7a74)
  • remove usage of node:path and process in browser build (2580aeb)

v8.0.1

Compare Source

Bug Fixes
  • fix nodejs code being included in browser bundle (7c76a3b)

v8.0.0

Compare Source

⚠ BREAKING CHANGES

See {@​link migration migration guide} for details.

  • api: The ConfigFactory parameter to ConfigLoader (and its child
    classes StaticConfigLoader and FileSystemConfigLoader) has been removed. No
    replacement.

If you are using this you are probably better off implementing a fully custom
loader later returning a ResolvedConfig.

  • api: A new getContextualDocumentation replaces the now deprecated
    getRuleDocumentation method. The context parameter to getRuleDocumentation
    is now required and must not be omitted.

For rule authors this means you can now rely on the context parameter being
set in the documentation callback.

For IDE integration and toolchain authors this means you should migrate to use
getContextualDocumentation as soon as possible or if you are continuing to use
getRuleDocumentation you are now required to pass the config and context
field from the reported message.

  • api: This change affect API users only, specifically API users
    directly using the Config class. Additionally when using the
    StaticConfigLoader no modules will be resolved using require(..) by default
    any longer. Instructions for running in a browser is also updated, see below.

To create a Config instance you must now pass in a Resolver (single or
array):

+const resolvers = [ /* ... */ ];
-const config = new Config( /* ... */ );
+const config = new Config(resolvers, /* ... */ );

This applies to calls to Config.fromObject(..) as well.

The default resolvers for StaticConfigLoader is StaticResolver and for
FileSystemConfigLoader is NodeJSResolver. Both can optionally take a new set
of resolvers (including custom ones).

Each resolver will, in order, try to load things by name. For instance, when
using the NodeJSResolver it uses require(..) to load new items.

  • NodeJSResolver - uses require(..)
  • StaticResolver - uses a predefined set of items.
  • api: The HtmlValidate class now has a Promise based API where most
    methods return a promise. The old synchronous methods are renamed.

Either adapt to the new asynchronous API:

-const result = htmlvalidate.validateFile("my-awesome-file.html");
+const result = await htmlvalidate.validateFile("my-awesome-file.html");

or migrate to the synchronous API:

-const result = htmlvalidate.validateFile("my-awesome-file.html");
+const result = htmlvalidate.validateFileSync("my-awesome-file.html");

For unittesting with Jest it is recommended to make the entire test-case async:

-it("my awesome test", () => {
+it("my awesome test", async () => {
   const htmlvalidate = new HtmlValidate();
-  const report = htmlvalidate.validateString("...");
+  const report = await htmlvalidate.validateString("...");
   expect(report).toMatchCodeFrame();
});
  • api: ConfigLoader must return ResolvedConfig. This change
    affects API users who implements custom configuration loaders.

In the simplest case this only requires to call Config.resolve():

-return config;
+return config.resolve();

A resolved configuration cannot further reference any new files to extend,
plugins to load, etc.

  • api: The TemplateExtractor class has been moved to the
    @html-validate/plugin-utils package. This change only affects API users who
    use the TemplateExtractor class, typically this is only used when writing
    plugins.
  • config: Deprecated severity alias disabled removed. If you use this in your
    configuration you need to update it to off.
 {
   "rules": {
-    "my-awesome-rule": "disabled"
+    "my-awesome-rule": "off"
   }
 }
  • rules: The void rule has been removed after being deprecated a long
    time, it is replaced with the separate void-content, void-style and
    no-self-closing rules.
  • deps: minimum required node version is v16
  • deps: minimum required jest version is v27
Features
  • api: ConfigLoader must return ResolvedConfig (d685e6a)
  • api: FileSystemConfigLoader supports passing a custom fs-like object (fac704e)
  • api: add Promise based API to HtmlValidate class (adc7783)
  • api: add Resolver classes as a mean to separate fs from browser build (3dc1724)
  • api: new getContextualDocumentation to replace getRuleDocumentation (60c9a12)
  • api: remove ConfigFactory (e309d89)
  • api: remove TemplateExtractor in favour of @html-validate/plugin-utils (a0a512b)
  • deps: minimum required jest version is v27 (dc79b6b)
  • deps: minimum required node version is v16 (f6ccdb0)
  • rules: remove deprecated void rule (3e727d8)
Bug Fixes
  • config: remove deprecated severity alias disabled (6282293)

v7.18.1

Compare Source

Bug Fixes
  • cli: error message on missing --config file (e948a18)

v7.18.0

Compare Source

Features
Bug Fixes
  • api: mark Config.fromFile() as internal (3e70028)
  • api: mark Config.getMetaTable() as internal (8cb6dd0)
  • api: mark dumpEvents,dumpSource, dumpTokens and dumpTree as internal (866f219)
  • jest: toMatchCodeframe and toMatchInlineCodeframe handles async result (584c67e)

v7.17.0

Compare Source

Features
  • allow to specify plugins inline in configuration (6ba1467)
Bug Fixes
  • rules: allow custom elements to use aria-label (513a813)

v7.16.0

Compare Source

Features
  • api: ConfigLoader returns a ResolvedConfig (1fd8b73)
Dependency upgrades

v7.15.3

Compare Source

Bug Fixes
  • api: remove unused url import (a2017ff)

v7.15.2

Compare Source

Bug Fixes
  • api: fix typescript not finding type declarations (0950bb9), closes #​217
  • rules: form-dup-name defaults to allow <button type="submit"> to share name (b39b9ad), closes #​212
Dependency upgrades
  • deps: update dependency glob to v10 (1855cf0)

v7.15.1

Compare Source

Bug Fixes
  • add missing exports (7fb141d)
  • fix html-validate/test-utils entrypoint (62fbee3)
  • include tsdoc-metadata.json (61dd7dd)

v7.15.0

Compare Source

Features
Bug Fixes
  • dom: querySelector typescript declaration returns null to match implementation (9c9befe)
  • fix browser entrypoint for older bundlers (c8320ba)

v7.14.0

Compare Source

Features
  • rules: add [role="alertdialog"] as a default sectioning root for heading-level (b87581a)
Bug Fixes
  • cli: fix glob pattern when file extension list is empty (d95a418)
Dependency upgrades
  • deps: update dependency glob to v9 (effd3bc)

v7.13.3

Compare Source

Bug Fixes
  • rules: check for empty alt tag in wcag/h37 (5f3b43f), closes #​209

v7.13.2

Compare Source

Bug Fixes
  • add button and reset types to form-dup-name shared options (d6ef9f8)

v7.13.1

Compare Source

Bug Fixes
  • no-unused-disable properly reports location when more than two rules are disabled (26d1970)
  • allow no-unused-disable to be disabled by directive (b11166c)

v7.13.0

Compare Source

Features

v7.12.2

Compare Source

Bug Fixes
  • form-dup-name validate checkboxes by default (d5e7b7d), closes #​202
  • add allowArrayBrackets option to form-dup-name rule (a43ea0b), closes #​203
  • add shared option to form-dup-name to set which controls allow shared names (7ddc02b), closes #​201

v7.12.1

Compare Source

Bug Fixes
  • rules: form-dup-name reports when radio and non-radio uses same name (6d9a282), closes #​200

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/html-validate-8.x branch 4 times, most recently from 5a3ad50 to 1ffeb15 Compare January 17, 2024 11:13
@mfranzke mfranzke enabled auto-merge (squash) January 17, 2024 11:20
@renovate renovate bot force-pushed the renovate/html-validate-8.x branch from 1ffeb15 to 28ff09c Compare January 17, 2024 11:20
mfranzke
mfranzke previously approved these changes Jan 17, 2024
@renovate renovate bot force-pushed the renovate/html-validate-8.x branch from 28ff09c to db189f2 Compare January 17, 2024 11:23
@mfranzke mfranzke merged commit 6bf4156 into main Jan 17, 2024
10 checks passed
@mfranzke mfranzke deleted the renovate/html-validate-8.x branch January 17, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant