fix(schema): remove default values from improved types

Using `z.default` adds `undefined` to generated types. Not sure why,
since I explicitly provide a default value so that the property cannot
be `undefined` but well...

More info:
https://stackoverflow.com/questions/76396222/zod-using-optional-with-default-infers-the-wrong-type

Author: pawcoding

README.md

@@ -108,9 +108,9 @@ The loader will also automatically convert the value into a slug to be easily us
 It's recommended to use e.g. the title of the entry to be easily searchable and readable.
 **Do not use e.g. rich text fields as ids.**
 
-### Improved type safety
+### Improved types
 
-By default PocketBase reports `number` and `boolean` fields as not required.
+By default PocketBase reports `number` and `boolean` fields as not required, even though the API will always return at least `0` and `false` respectively.
 This means that the loader will add `undefined` to the type of these fields.
 If you want to enforce that these fields are always present, you can set the `improveTypes` option to `true`.
 
@@ -123,8 +123,7 @@ const blog = defineCollection({
 });
 ```
 
-This will remove `undefined` from the type of these fields and provide default values with `0` and `false` respectively.
-PocketBase will also use these default values when creating new entries in the dashboard.
+This will remove `undefined` from the type of these fields and mark them as required.
 
 ## Type generation
 

src/types/pocketbase-loader-options.type.ts

@@ -67,11 +67,10 @@ export interface PocketBaseLoaderOptions {
   jsonSchemas?: Record<string, z.ZodSchema>;
   /**
    * Whether to improve the types of the generated schema.
-   * This includes providing `0` or `false` as default values for number and boolean fields, respectively.
-   * With this option enabled, the schema will not generate `undefined` as possible value for number and boolean fields.
+   * With this option enabled, the schema will not include `undefined` as possible value for number and boolean fields and mark them as required.
    *
    * Why do we need this option?
-   * PocketBase does use these values as the default values, even though it's not specified in the schema.
+   * The PocketBase API does always return at least `0` or `false` as the default values, even though the fields are not marked as required in the schema.
    */
   improveTypes?: boolean;
 }

src/utils/parse-schema.ts

@@ -26,11 +26,11 @@ export function parseSchema(
     switch (field.type) {
       case "number":
         // Coerce the value to a number
-        fieldType = z.coerce.number();
+        fieldType = z.number();
         break;
       case "bool":
         // Coerce the value to a boolean
-        fieldType = z.coerce.boolean();
+        fieldType = z.boolean();
         break;
       case "date":
       case "autodate":
@@ -82,19 +82,6 @@ export function parseSchema(
       // Improve number and boolean types by providing default values
       (improveTypes && (field.type === "number" || field.type === "bool"));
 
-    if (improveTypes) {
-      switch (field.type) {
-        case "number":
-          // If the field is a number, provide a default value of 0
-          fieldType = fieldType.default(0);
-          break;
-        case "bool":
-          // If the field is a boolean, provide a default value of false
-          fieldType = fieldType.default(false);
-          break;
-      }
-    }
-
     // If the field is not required, mark it as optional
     if (!isRequired) {
       fieldType = z.preprocess(