Validation of a string or number that is not performing as expected

Question

Validation of a string or number that is not performing as expected

I have been working with the yup library for JavaScript data validation, but I am encountering unexpected behavior. Despite thoroughly reviewing their documentation, I cannot pinpoint where I am misusing their API. When I run the unit test below, it fails when I expect it to pass. Any suggestions on what might be causing this issue?

import { object, string } from 'yup';

test('validator', async () => {
  let schema = object({
    name: string(),
  });

  expect(await schema.isValid({ name: 123 })).toEqual(false);
});

I am using version

"yup": "^0.32.11"

I attempted to run this validation within a Jest unit test and it failed. I also looked into other validation methods in their API docs.

javascript json validation yup

Answer 1

Answer №1

The outcome follows the expected pattern due to the implementation of the yup library. Utilizing the strict option in a schema prevents the execution of the yup parser, thereby eliminating the chance of converting your number value into a string value through type coercion. When the strict option is enabled, the number value of 123 will undergo validation without type coercion. Consequently, since it is not a string value, the validation will be unsuccessful. In contrast, when the strict option is disabled, type coercion takes place resulting in successful validation.

Answer 2

The outcome follows the expected pattern due to the implementation of the yup library. Utilizing the strict option in a schema prevents the execution of the yup parser, thereby eliminating the chance of converting your number value into a string value through type coercion. When the strict option is enabled, the number value of 123 will undergo validation without type coercion. Consequently, since it is not a string value, the validation will be unsuccessful. In contrast, when the strict option is disabled, type coercion takes place resulting in successful validation.

Validation of a string or number that is not performing as expected

Answer №1

Similar questions

When moving from Babel version 5.8.35 to 6.0.0, be prepared for app.js to throw a SyntaxError and encounter an unexpected token during compilation

Click on the navigation bar buttons to toggle between different divs and display multiple information boxes simultaneously

Unlimited digest loop in Angular.js caused by nested ng-repeat and filter

Enhancing UI Design with Styled-Components and Material Components using Media Queries

Ensure Next.js retains the route when moving from one screen to another

Is there a way to transfer JavaScript data to PHP?

The file could not be loaded as a result of Multipart: The boundary was not detected

Transforming the code from numerous div elements to utilizing Ajax for efficient execution

Adding dynamic metadata to a specific page in a next.js app using the router

What causes the issue of text being blocked by a webgl shader background even when the text div is layered above and given a higher z-index?

The background image causes the scrollbar to vanish

Deactivate specific ASP.Net validation controls upon checking a checkbox

Effortless Android JSON Decoding

What is the best way to transform api.Response into a data frame or json format using Python?

Is Cognito redirect causing issues with Angular router responsiveness?

Filtering React component names and their corresponding values

Translating jsonObject into a Map in the Scala programming language

Unable to assign value to Ref data property in Vue3 due to undefined item

What role does the "deep" parameter serve when declaring a watcher in VueJS?

Challenges in handling asynchronous data within static JSON objects in Angular2