cleanup for potential merge

Author: heskew

config.yaml

@@ -14,5 +14,4 @@ static: # This allows static files to be directly accessible
 roles: # This can define the roles that are used in the application
   files: roles.yaml
 dataLoader: # This loads data into user tables from YAML or JSON files
-  files: data/*.{json,yaml,yml}
-  # forceLoad: true  # Uncomment to force loading data even if tables already have records
+  files: data/*.{json,yaml,yml}

data/README.md

@@ -17,7 +17,7 @@ Data files must contain `table` and `records` fields. The `database` field is op
 
 ### JSON Example
 
-```json
+```jsonc
 {
   "database": "dev",       // Optional - uses default database if omitted
   "table": "Product",      // Required - name of the table
@@ -45,11 +45,13 @@ records:                   # Required - array of records
 ## Key Features
 
 - **Automatic Table Creation**: Tables are created if they don't exist
-- **Primary Key Detection**: The `id` field is automatically detected as the primary key
+- **Schema Inference**:
+  - The system will automatically infer a schema from the first record when creating a new table
+  - The `id` field is automatically detected as the primary key
+  - It's preferred to define the schema explicitly in your application, but this provides a quick start
 - **File Modification Time**:
   - The data loader uses the file's modification time (`mtime`) to determine if records should be updated
   - "Touching" a file (updating its modification time) will force a reload of its data
-  - This allows for simpler data files without timestamp properties in the records
 - **Multi-file Support**: You can have multiple data files for different tables
 - **Complex Data Types**: Supports nested objects, arrays, and various data types
 - **One Table Per File**: Each file should define one table
@@ -62,12 +64,4 @@ records:                   # Required - array of records
   touch data/products.json
   ```
 - If you need to restore to previous data, you can replace the file and update its timestamp
-- The system automatically handles the comparison between file modification time and record timestamps
-
-## Sample Files
-
-- `categories.json`: Category data with parent/child relationships
-- `products.json`: Product data with references to categories
-- `users.json`: User account data
-
-These sample files demonstrate common data patterns and relationships.
+- The system automatically handles the comparison between file modification time and record timestamps

data/categories.json

@@ -8,38 +8,3 @@ type TableName @table @export {
     name: String # we can define any other attributes here
     tag: String @indexed # we can specify any attributes that should be indexed
 }
-
-## Example tables for data loader example
-type Product @table @export {
-    id: ID @primaryKey
-    name: String @indexed
-    price: Float
-    category: Category @relationship(from: categoryId)
-    details: Any
-    inStock: Boolean
-}
-
-type Category @table @export {
-    id: ID @primaryKey
-    name: String @indexed
-    description: String
-    parent: Category @relationship(from: categoryId)
-    products: [Product] @relationship(to: categoryId)
-    children: [Category] @relationship(to: categoryId)
-}
-
-type User @table @export {
-    id: ID @primaryKey
-    username: String @indexed
-    email: String @indexed
-    firstName: String
-    lastName: String
-}
-
-type MycoUser @table(database: "myco", table: "User") @export {
-    id: ID @primaryKey
-    username: String @indexed
-    email: String @indexed
-    firstName: String
-    lastName: String
-}