Add parse options to is()

library/src/methods/is/is.test.ts

@@ -19,7 +19,8 @@ describe('is', () => {
     expect(is(object({ test: string() }), {})).toBe(false);
   });
 
-  test('should skip pipelines', () => {
-    expect(is(string([minLength(1)]), '')).toBe(true);
+  test('should accept parsing options', () => {
+    expect(is(string([minLength(1)]), '', { skipPipe: true })).toBe(true);
+    expect(is(string([minLength(1)]), '', { skipPipe: false })).toBe(false);
   });
 });

library/src/methods/is/is.ts

@@ -1,17 +1,19 @@
-import type { BaseSchema, Input } from '../../types.ts';
+import type { BaseSchema, Input, ParseInfo } from '../../types.ts';
 
 /**
  * Checks if the input matches the scheme. By using a type predicate, this
  * function can be used as a type guard.
  *
  * @param schema The schema to be used.
  * @param input The input to be tested.
+ * @param info The optional parse info.
  *
  * @returns Whether the input matches the scheme.
  */
 export function is<TSchema extends BaseSchema>(
   schema: TSchema,
-  input: unknown
+  input: unknown,
+  info?: ParseInfo
 ): input is Input<TSchema> {
-  return !schema._parse(input, { abortEarly: true, skipPipe: true }).issues;
+  return !schema._parse(input, { abortEarly: true, ...info }).issues;
 }

website/src/routes/guides/(main-concepts)/parse-data/index.mdx

@@ -51,7 +51,7 @@ if (result.success) {
 
 Another way to validate data that can be useful in individual cases is to use a type guard. A type guard is an if-condition which, if `true`, sets the parsed data to the input type of a schema.
 
-If a type guard is used, the issues of the validation cannot be accessed. Also, pipelines are skipped, transformations have no effect and unknown keys of an object are not removed. Therefore, this approach is not as safe and powerful as the two previous ways. Also, it can currently only be used with syncronous schemas.
+If a type guard is used, the issues of the validation cannot be accessed. Also, transformations have no effect and unknown keys of an object are not removed. Therefore, this approach is not as safe and powerful as the two previous ways. Also, it can currently only be used with syncronous schemas.
 
 ```ts
 import { email, is, string } from 'valibot'; // 0.55 kB