@vaadin/number-field - npm Package Compare versions

Comparing version 24.6.0-alpha7 to 24.6.0-alpha8

package.json

 {
   "name": "@vaadin/number-field",
-  "version": "24.6.0-alpha7",
+  "version": "24.6.0-alpha8",
   "publishConfig": {
@@ -39,13 +39,13 @@ "access": "public"
     "@polymer/polymer": "^3.0.0",
-    "@vaadin/a11y-base": "24.6.0-alpha7",
-    "@vaadin/component-base": "24.6.0-alpha7",
-    "@vaadin/field-base": "24.6.0-alpha7",
-    "@vaadin/input-container": "24.6.0-alpha7",
-    "@vaadin/vaadin-lumo-styles": "24.6.0-alpha7",
-    "@vaadin/vaadin-material-styles": "24.6.0-alpha7",
-    "@vaadin/vaadin-themable-mixin": "24.6.0-alpha7",
+    "@vaadin/a11y-base": "24.6.0-alpha8",
+    "@vaadin/component-base": "24.6.0-alpha8",
+    "@vaadin/field-base": "24.6.0-alpha8",
+    "@vaadin/input-container": "24.6.0-alpha8",
+    "@vaadin/vaadin-lumo-styles": "24.6.0-alpha8",
+    "@vaadin/vaadin-material-styles": "24.6.0-alpha8",
+    "@vaadin/vaadin-themable-mixin": "24.6.0-alpha8",
     "lit": "^3.0.0"
   },
   "devDependencies": {
-    "@vaadin/chai-plugins": "24.6.0-alpha7",
+    "@vaadin/chai-plugins": "24.6.0-alpha8",
     "@vaadin/testing-helpers": "^1.0.0",
@@ -58,3 +58,3 @@ "sinon": "^18.0.0"
   ],
-  "gitHead": "675d6fe0a08b8cc63ac00140c63f28fc3f52e4ea"
+  "gitHead": "a11e1510c4caa08775b202714f5fc1198c22132a"
 }

src/vaadin-number-field-mixin.js

@@ -514,6 +514,6 @@ /**
       if (this.__committedValue !== this.value) {
-        this.validate();
+        this._requestValidation();
         this.dispatchEvent(new CustomEvent('change', { bubbles: true }));
       } else if (this.__committedUnparsableValueStatus !== this.__hasUnparsableValue) {
-        this.validate();
+        this._requestValidation();
         this.dispatchEvent(new CustomEvent('unparsable-change'));
@@ -520,0 +520,0 @@ }

web-types.json

 {
   "$schema": "https://json.schemastore.org/web-types",
   "name": "@vaadin/number-field",
-  "version": "24.6.0-alpha7",
+  "version": "24.6.0-alpha8",
   "description-markup": "markdown",
@@ -11,3 +11,3 @@ "contributions": {
           "name": "vaadin-number-field",
-          "description": "`<vaadin-number-field>` is an input field web component that only accepts numeric input.\n\n```html\n<vaadin-number-field label=\"Balance\"></vaadin-number-field>\n```\n\n### Styling\n\n`<vaadin-number-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.\nSee [`<vaadin-text-field>`](https://cdn.vaadin.com/vaadin-web-components/24.6.0-alpha7/#/elements/vaadin-text-field) for the styling documentation.\n\nIn addition to `<vaadin-text-field>` parts, the following parts are available for theming:\n\nPart name         | Description\n------------------|-------------------------\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nNote, the `input-prevented` state attribute is only supported when `allowedCharPattern` is set.\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change             | Event\n:------------------------|:------------------\nempty => parsable        | change\nempty => unparsable      | unparsable-change\nparsable => empty        | change\nparsable => parsable     | change\nparsable => unparsable   | change\nunparsable => empty      | unparsable-change\nunparsable => parsable   | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
+          "description": "`<vaadin-number-field>` is an input field web component that only accepts numeric input.\n\n```html\n<vaadin-number-field label=\"Balance\"></vaadin-number-field>\n```\n\n### Styling\n\n`<vaadin-number-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.\nSee [`<vaadin-text-field>`](https://cdn.vaadin.com/vaadin-web-components/24.6.0-alpha8/#/elements/vaadin-text-field) for the styling documentation.\n\nIn addition to `<vaadin-text-field>` parts, the following parts are available for theming:\n\nPart name         | Description\n------------------|-------------------------\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nNote, the `input-prevented` state attribute is only supported when `allowedCharPattern` is set.\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change             | Event\n:------------------------|:------------------\nempty => parsable        | change\nempty => unparsable      | unparsable-change\nparsable => empty        | change\nparsable => parsable     | change\nparsable => unparsable   | change\nunparsable => empty      | unparsable-change\nunparsable => parsable   | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
           "attributes": [
@@ -59,2 +59,13 @@ {
             {
+              "name": "manual-validation",
+              "description": "Set to true to enable manual validation mode. This mode disables automatic\nconstraint validation, allowing you to control the validation process yourself.\nYou can still trigger constraint validation manually with the `validate()` method\nor use `checkValidity()` to assess the component's validity without affecting\nthe invalid state. In manual validation mode, you can also manipulate\nthe `invalid` property directly through your application logic without conflicts\nwith the component's internal validation.",
+              "value": {
+                "type": [
+                  "boolean",
+                  "null",
+                  "undefined"
+                ]
+              }
+            },
+            {
               "name": "required",
@@ -336,2 +347,13 @@ "description": "Specifies that the user must fill in a value.",
               {
+                "name": "manualValidation",
+                "description": "Set to true to enable manual validation mode. This mode disables automatic\nconstraint validation, allowing you to control the validation process yourself.\nYou can still trigger constraint validation manually with the `validate()` method\nor use `checkValidity()` to assess the component's validity without affecting\nthe invalid state. In manual validation mode, you can also manipulate\nthe `invalid` property directly through your application logic without conflicts\nwith the component's internal validation.",
+                "value": {
+                  "type": [
+                    "boolean",
+                    "null",
+                    "undefined"
+                  ]
+                }
+              },
+              {
                 "name": "required",
@@ -338,0 +360,0 @@ "description": "Specifies that the user must fill in a value.",

web-types.lit.json

 {
   "$schema": "https://json.schemastore.org/web-types",
   "name": "@vaadin/number-field",
-  "version": "24.6.0-alpha7",
+  "version": "24.6.0-alpha8",
   "description-markup": "markdown",
@@ -19,3 +19,3 @@ "framework": "lit",
           "name": "vaadin-number-field",
-          "description": "`<vaadin-number-field>` is an input field web component that only accepts numeric input.\n\n```html\n<vaadin-number-field label=\"Balance\"></vaadin-number-field>\n```\n\n### Styling\n\n`<vaadin-number-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.\nSee [`<vaadin-text-field>`](https://cdn.vaadin.com/vaadin-web-components/24.6.0-alpha7/#/elements/vaadin-text-field) for the styling documentation.\n\nIn addition to `<vaadin-text-field>` parts, the following parts are available for theming:\n\nPart name         | Description\n------------------|-------------------------\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nNote, the `input-prevented` state attribute is only supported when `allowedCharPattern` is set.\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change             | Event\n:------------------------|:------------------\nempty => parsable        | change\nempty => unparsable      | unparsable-change\nparsable => empty        | change\nparsable => parsable     | change\nparsable => unparsable   | change\nunparsable => empty      | unparsable-change\nunparsable => parsable   | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
+          "description": "`<vaadin-number-field>` is an input field web component that only accepts numeric input.\n\n```html\n<vaadin-number-field label=\"Balance\"></vaadin-number-field>\n```\n\n### Styling\n\n`<vaadin-number-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.\nSee [`<vaadin-text-field>`](https://cdn.vaadin.com/vaadin-web-components/24.6.0-alpha8/#/elements/vaadin-text-field) for the styling documentation.\n\nIn addition to `<vaadin-text-field>` parts, the following parts are available for theming:\n\nPart name         | Description\n------------------|-------------------------\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nNote, the `input-prevented` state attribute is only supported when `allowedCharPattern` is set.\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change             | Event\n:------------------------|:------------------\nempty => parsable        | change\nempty => unparsable      | unparsable-change\nparsable => empty        | change\nparsable => parsable     | change\nparsable => unparsable   | change\nunparsable => empty      | unparsable-change\nunparsable => parsable   | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
           "extension": true,
@@ -45,2 +45,9 @@ "attributes": [
             {
+              "name": "?manualValidation",
+              "description": "Set to true to enable manual validation mode. This mode disables automatic\nconstraint validation, allowing you to control the validation process yourself.\nYou can still trigger constraint validation manually with the `validate()` method\nor use `checkValidity()` to assess the component's validity without affecting\nthe invalid state. In manual validation mode, you can also manipulate\nthe `invalid` property directly through your application logic without conflicts\nwith the component's internal validation.",
+              "value": {
+                "kind": "expression"
+              }
+            },
+            {
               "name": "?required",
@@ -47,0 +54,0 @@ "description": "Specifies that the user must fill in a value.",

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

84380

increased by2.82%

Lines of code

1883

increased by1.73%

Dependency changes

• + Added@vaadin/a11y-base@24.6.0-alpha8(transitive)

• + Added@vaadin/component-base@24.6.0-alpha8(transitive)

• + Added@vaadin/field-base@24.6.0-alpha8(transitive)

• + Added@vaadin/icon@24.6.0-alpha8(transitive)

• + Added@vaadin/input-container@24.6.0-alpha8(transitive)

• + Added@vaadin/vaadin-lumo-styles@24.6.0-alpha8(transitive)

• + Added@vaadin/vaadin-material-styles@24.6.0-alpha8(transitive)

• + Added@vaadin/vaadin-themable-mixin@24.6.0-alpha8(transitive)

• - Removed@vaadin/a11y-base@24.6.0-alpha7(transitive)

• - Removed@vaadin/component-base@24.6.0-alpha7(transitive)

• - Removed@vaadin/field-base@24.6.0-alpha7(transitive)

• - Removed@vaadin/icon@24.6.0-alpha7(transitive)

• - Removed@vaadin/input-container@24.6.0-alpha7(transitive)

• - Removed@vaadin/vaadin-lumo-styles@24.6.0-alpha7(transitive)

• - Removed@vaadin/vaadin-material-styles@24.6.0-alpha7(transitive)

• - Removed@vaadin/vaadin-themable-mixin@24.6.0-alpha7(transitive)

• Updated@vaadin/a11y-base@24.6.0-alpha8

• Updated@vaadin/component-base@24.6.0-alpha8

• Updated@vaadin/field-base@24.6.0-alpha8

• Updated@vaadin/input-container@24.6.0-alpha8

• Updated@vaadin/vaadin-lumo-styles@24.6.0-alpha8

• Updated@vaadin/vaadin-material-styles@24.6.0-alpha8

• Updated@vaadin/vaadin-themable-mixin@24.6.0-alpha8