Page : https://www.totaltypescript.com/tutorials/zod/optional/solution

some weird behavior on this page only, the screen flickers continuously on my large-resolution monitor but works fine for monitor with small resolution. Screen Size: 1920px × 1080px

I've attached video but unfortunately, my screen recorder couldn't capture the fps on which the screen is flickering.

https://user-images.githubusercontent.com/50266088/194393200-d6953aa6-e481-453e-af03-7a4f313c5f3e.mp4

Hi there,

Thank you very much for such great tutorials. One small thing - there is a typo I think on the tutorial environment. Not sure where to mention it, maybe in this repo.

I guess it should be "Extract a type from a Parser Object"

Apologies if that's not the right place to mention this kind of things. Thanks again for the amazing tutorial!

thanks for helpful tutorial :) i had never know zod before i know this tutorial. i think adding problem about zod's record is very helpful.

how do you think about my suggestion?

if you like i will add new problem for zod record

I often happens in form validation that you have to compare two date fields, like from -> to, that is also possible in zod with refine as far as I remember.

The previous PR removed the mention of the YouTube video (which was included as a TODO previously). This further cleans up the README by removing the other reference to using a video.

I'm not sure whether the video is still planned to be included, but until it is it might be best to avoid confusion!

I'm using

• Windows 11
• Node v16.15.1

When executed the exercise script, e.g. yarn exercise 01, it runs tests for all problems instead of the particular problem

Hi, Matt!

Really enjoying the tutorial and carefully reading every sentence 🤓

Should this read "... to pass any invalid email, phone number, or website url."? I reckon it should, since you speak about them in the video, but the inputs are singular.

Keep on the great work! Cheers

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Exercise 07 solutions don't contain the "or" usage alternative

Fixes: #4

What is the new behavior?

Exercise 07 has a third solution using the "or" function from Zod

name: Feature request about: Suggest an idea for this project title: 'add "or" solution to "07 union problem"'

What is the motivation/use case for changing the behavior?

When discussing the possible solutions for exercise 07, it would be nice to include the use of "or" as a union alternative.

Describe the solution you'd like

Add the following as a third solution.

const Form = z.object({
  repoName: z.string(),
  privacyLevel: z.literal('private').or(z.literal('public')),
});

Currently both of these "solutions" pass exercise 14:

// correct
const genericFetch = <Schema extends z.ZodSchema>(
  url: string,
  schema: Schema
): Promise<z.infer<Schema>> => {
  return fetch(url)
    .then((res) => res.json())
    .then((result) => schema.parse(result));
};

// incorrect, doesn't return a promise
const genericFetch = <Schema extends z.ZodSchema>(
  url: string,
  schema: Schema
): z.infer<Schema> => {
  return fetch(url)
    .then((res) => res.json())
    .then((result) => schema.parse(result));
};

This is because the current test case checks the type of result, which awaits genericFetch, so it doesn't care if genericFetch returns a Promise or not.

I came up with two possibilities for a test case that catches this - I don't love either of these, maybe a TS Wizard could come up with something more elegant.

1. Just check that genericFetch returns a promise of some sort

Expect<Equal<ReturnType<typeof genericFetch>, Promise<z.TypeOf<any>>>>

2. Check the entire type of genericFetch

Expect<
  Equal<
    typeof genericFetch,
    <Schema extends z.ZodType<any, z.ZodTypeDef, any>>(
      url: string,
      schema: Schema
    ) => Promise<z.TypeOf<Schema>>
  >
>