@rettangoli/fe 0.0.6 → 0.0.7-rc2

package/README.md

@@ -1,164 +1,267 @@
-
 # Rettangoli Frontend
 
-## Development
+A modern frontend framework that uses YAML for view definitions, web components for composition, and Immer for state management. Build reactive applications with minimal complexity using just 3 types of files.
 
-Bundle the code under `example` folder using `@rettangoli/fe`
+## Features
 
-```bash
-bun run ../rettangoli-cli/cli.js fe build
-```
+- **🗂️ Three-File Architecture** - `.view.yaml`, `.store.js`, `.handlers.js` files scale from single page to complex applications
+- **📝 YAML Views** - Declarative UI definitions that compile to virtual DOM
+- **🧩 Web Components** - Standards-based component architecture
+- **🔄 Reactive State** - Immer-powered immutable state management
+- **⚡ Fast Development** - Hot reload with Vite integration
+- **🎯 Template System** - Jempl templating for dynamic content
+- **🧪 Testing Ready** - Pure functions and dependency injection for easy testing
 
-Visit the example project that shows the components in action
+## Quick Start
 
+**Production usage** (when rtgl is installed globally):
 ```bash
-bunx serve ./viz/static
+rtgl fe build     # Build components
+rtgl fe watch     # Start dev server
+rtgl fe scaffold  # Create new component
 ```
 
-Instead of running `fe build` each time, we can also watch for file changes and bundle the code automatically.
+## Architecture
 
-```bash
-bun run ../rettangoli-cli/cli.js fe watch
-```
+### Technology Stack
 
+**Runtime:**
+- [Snabbdom](https://github.com/snabbdom/snabbdom) - Virtual DOM
+- [Immer](https://github.com/immerjs/immer) - Immutable state management
+- [Jempl](https://github.com/yuusoft-org/jempl) - Template engine
+- [RxJS](https://github.com/ReactiveX/rxjs) - Reactive programming
 
-Note: rettangoli-vt is not setup for this project yet. We just use static files under `viz/static` folder.
+**Build & Development:**
+- [ESBuild](https://esbuild.github.io/) - Fast bundling
+- [Vite](https://vite.dev/) - Development server with hot reload
 
+**Browser Native:**
+- Web Components - Component encapsulation
 
-## Introduction
+## Development
 
-A frontend framework with just 3 type of files to scale from a single page to a full fledged complex application.
+### Prerequisites
 
-Implemented using:
+- Node.js 18+ or Bun
+- A `rettangoli.config.yaml` file in your project root
 
-Browser native:
-* web components for components
+### Setup
 
-Runtime:
-* [snabbdom](https://github.com/snabbdom/snabbdom) for virtual dom
-* [immer](https://github.com/immerjs/immer) for data immutability for state management
-* [json-e](https://github.com/json-e/json-e) for templating using json
-* [rxjs](https://github.com/ReactiveX/rxjs) for reactive programming
+1. **Install dependencies**:
+```bash
+bun install
+```
 
-Build & Development:
-* [esbuild](https://esbuild.github.io/) for bundling
-* [vite](https://vite.dev/) for development
+2. **Create project structure**:
+```bash
+# Scaffold a new component
+node ../rettangoli-cli/cli.js fe scaffold --category components --name MyButton
+```
 
-## View Layer
+3. **Start development**:
+```bash
+# Build once
+node ../rettangoli-cli/cli.js fe build
 
-The view layer is unique in that it uses yaml.
+# Watch for changes (recommended)
+node ../rettangoli-cli/cli.js fe watch
+```
 
-* The yaml will be converted into json at build time. The json will then be consumed by snabbdom to be transformed into html through a virtual dom.
+### Project Structure
 
-### Yaml to write html
+```
+src/
+├── cli/
+│   ├── build.js       # Build component bundles
+│   ├── watch.js       # Development server with hot reload
+│   ├── scaffold.js    # Component scaffolding
+│   ├── examples.js    # Generate examples for testing
+│   └── blank/         # Component templates
+├── createComponent.js # Component factory
+├── createWebPatch.js  # Virtual DOM patching
+├── parser.js          # YAML to JSON converter
+├── common.js          # Shared utilities
+└── index.js           # Main exports
+```
 
-Standard html can be totally written in yaml. 
+# Usage
 
-All child element are arrays. Except for things like actual content of text
+## Component Structure
 
-Use `#` and `.` selectors to represent `id` and `class`.
+Each component consists of three files:
 
-`div#myid.class1.class2 custorm-attribute=abcd`
+```
+component-name/
+├── component-name.handlers.js   # Event handlers
+├── component-name.store.js      # State management
+└── component-name.view.yaml     # UI structure and styling
+```
 
-will become
 
-`<div id="myid" class="class1 class2" custom-attribute="abcd"></div>`
+## View Layer (.view.yaml)
 
+Views are written in YAML and compiled to virtual DOM at build time.
 
-### Templating using json-e
+### Basic HTML Structure
 
-`json-e` templating language allows us to write conditions and loops in our yaml. For example:
+```yaml
+template:
+  - div#myid.class1.class2 custom-attribute=abcd:
+    - rtgl-text: "Hello World"
+    - rtgl-button: "Click Me"
+```
 
+Compiles to:
+```html
+<div id="myid" class="class1 class2" custom-attribute="abcd">
+  <rtgl-text>Hello World</rtgl-text>
+  <rtgl-button>Click Me</rtgl-button>
+</div>
+```
 
-Loop
+### Component Definition
 
 ```yaml
+elementName: my-custom-component
+
 template:
-  - rtgl-view w=f g=m:
-    - $map: { $eval: projects }
-      each(v,k):
-        - rtgl-view#project-${v.id} h=64 w=f bw=xs p=m cur=p:
-          - rtgl-text s=lg: "${v.name}"
-          - rtgl-text s=sm: "${v.description}"
+  - rtgl-view:
+    - rtgl-text: "My Component"
 ```
 
-Conditional. We usually use `$switch` more as it tends to be more flexible than `$if`.
+### Attributes vs Props
+
+When passing data to components, there's an important distinction:
 
 ```yaml
 template:
-  - rtgl-view d=h w=f h=f:
-    - $switch:
-        'showSidebar':
-          - sidebar-component: []
-    - rtgl-view w=f h=f:
-      - $switch:
-          'currentRoute== "/projects"':
-            - projects-component: []
-          'currentRoute== "/profile"':
+  - custom-component title=Hello .items=items
 ```
 
-`json-e` has many more features but we want to keep it simple and in most cases loops and conditionals are enough.
+- **Attributes** (`title=Hello`): Always string values, passed as HTML attributes
+- **Props** (`.items=items`): JavaScript values from viewData, passed as component properties
+
+Attributes become HTML attributes, while props are JavaScript objects/arrays/functions passed directly to the component.
 
-The actual data used in the template is passed in as `viewData` from the state store which we will cover later.
+### Variable Expressions
 
-### Define a elementName
+Views do not support complex variable expressions like `${myValue || 4}`. All values must be pre-computed in the `toViewData` store function:
 
+❌ **Don't do this:**
 ```yaml
-elementName: custom-projects
+template:
+  - rtgl-text: "${user.name || 'Guest'}"
+  - rtgl-view class="${isActive ? 'active' : 'inactive'}"
+```
+
+✅ **Do this instead:**
+```js
+// In your .store.js file
+export const toViewData = ({ state, props, attrs }) => {
+  return {
+    ...state,
+    displayName: state.user.name || 'Guest',
+    statusClass: state.isActive ? 'active' : 'inactive'
+  };
+};
 ```
 
-This will be the web component name that will be used for the component.
+```yaml
+template:
+  - rtgl-text: "${displayName}"
+  - rtgl-view class="${statusClass}"
+```
 
-The component can later be used as `<custom-projects></custom-projects>`.
 
-### Styles
 
-Styles can also be completely written in yaml.
+### Styling
 
 ```yaml
 styles:
   '#title':
     font-size: 24px
+    color: blue
   '@media (min-width: 768px)':
     '#title':
       font-size: 32px
 ```
 
-TODO better support nesting and issue with some global selectors.
-
-### Event listeners
+### Event Handling
 
 ```yaml
 refs:
-  createButton:
-    eventListeners:
-      click:
-        handler: handleCreateButtonClick
-  project-*:
+  submitButton:
     eventListeners:
       click:
-        handler: handleProjectsClick
+        handler: handleSubmit
+
+template:
+  - rtgl-button#submitButton: "Submit"
+```
+
+### Templating with Jempl
+
+**Loops:**
+```yaml
+template:
+  - rtgl-view:
+      projects:
+        $for project, index in projects:
+          - rtgl-view#project-${project.id}:
+            - rtgl-text: "${project.name}"
+            - rtgl-text: "${project.description}"
+            - rtgl-text: "Item ${index}"
+```
+
+
+#### Props caveats
+
+❌ This will not work. Prop references can only be taken from viewDate, not from loop variables
+
+```yaml
+
+template:
+  - rtgl-view:
+    - $for project, index in projects:
+      - rtgl-view#project-${project.id}:
+        - custom-component .item=project: 
+```
+
+✅ This is the workaround
 
+```yaml
 template:
-  - rtgl-button#createButton: Create Project
-  - rtgl-view w=f g=m:
-    - $map: { $eval: projects }
-      each(v,k):
-        - rtgl-view#project-${v.id} h=64 w=f bw=xs p=m cur=p:
-          - rtgl-text s=lg: "${v.name}"
-          - rtgl-text s=sm: "${v.description}"
+  - rtgl-view:
+    - $for project, index in projects:
+      - rtgl-view#project-${project.id}:
+        - custom-component .item=projects[${index}]: 
 ```
 
-The above example, will attach event listenrs to `#createButton` and all `#project-*` (wild card support) elements. And bind them to the handlers `handleCreateButtonClick` and `handleProjectsClick`.
+**Conditionals:**
+```yaml
+template:
+  - rtgl-view:
+      $if isLoggedIn:
+        - user-dashboard: []
+      $else:
+        - login-form: []
 
-### Defining data schema
+# Multiple conditions with logical operators
+template:
+  - rtgl-view:
+      $if user.age >= 18 && user.verified:
+        - admin-panel: []
+      $elif user.age >= 13:
+        - teen-dashboard: []
+      $else:
+        - kid-dashboard: []
+```
 
-Component have a few types of data that can be defined using a JSON schema:
+For more advanced templating features, see the [Jempl documentation](https://github.com/yuusoft-org/jempl).
 
-* `viewDataSchema` - The data that will used for the template.
-* `propsSchema` - The data that will be passed to the component via javascript, those can be objects.
-* `attrsSchema` - The data that will be passed to the component via html attributes, this is raw strings.
+### Data Schemas
 
+Define component interfaces with JSON Schema:
 
 ```yaml
 viewDataSchema:
@@ -166,159 +269,176 @@ viewDataSchema:
   properties:
     title:
       type: string
-      default: Projects
-    createButtonText:
-      type: string
-      default: Create Project
-    projects:
+      default: "My Component"
+    items:
       type: array
       items:
         type: object
-        properties:
-          id:
-            type: string
-          name:
-            type: string
-            default: Project 1
-          description:
-            type: string
-            default: Project 1 description
+
 propsSchema:
   type: object
-  properties: {}
-```
+  properties:
+    onSelect:
+      type: function
 
+attrsSchema:
+  type: object
+  properties:
+    variant:
+      type: string
+      enum: [primary, secondary]
+```
 
-## State Store
+## State Management (.store.js)
 
-* Define `initial state`
-* `toViewData` will take current `state`, `props` and `attrs` and return the `viewData` to be used by the view template
-* Any exported function that starts with `select`  will beceme selectors and are used by handlers to access state data
-* `actions` are all other exported functions that are used to mutate the state.
+### Initial State
 
 ```js
 export const INITIAL_STATE = Object.freeze({
-  title: "Projects",
-  createButtonText: "Create Project",
-  projects: [
-    {
-      id: "1",
-      name: "Project 1",
-      description: "Project 1 description",
-    },
-    {
-      id: '2',
-      name: 'Project 2',
-      description: 'Project 2 description'
-    }
-  ],
+  title: "My App",
+  items: [],
+  loading: false
 });
-
-export const toViewData = ({ state, props }, payload) => {
-  return state;
-}
-
-export const selectProjects = (state, props, payload) => {
-  return state.projects;
-}
-
-export const setProjects = (state, payload) => {
-
-}
 ```
 
-Note that this is just a dump store, it is not reactive. Components will need to call `deps.render()` from handlers to re-render the component.
-
-## Handlers
+### View Data Transformation
 
-`handleOnMount` is a special handler that is called when the component is mounted. It returns a promise that resolves when the component is mounted.
-
-All other exported functions will automatically become handlers and can be used in the view layers's `eventListeners`
+```js
+export const toViewData = ({ state, props, attrs }) => {
+  return {
+    ...state,
+    itemCount: state.items.length,
+    hasItems: state.items.length > 0
+  };
+};
+```
 
-A special object called `deps` is injected into all handlers. It has the following properties:
+### Selectors
 
-* `deps.render()` will re-render the component. We call this function each time we have chaged state and want to re-render the component.
-* `deps.store` is the store instance. Use selectors to select state and actions to mutate state.
-* `deps.transformedHandlers` can be used to call other handlers.
-* `deps.attrs` is the html attributes that are passed to the component.
-* `deps.props` is the javascript properties that are passed to the component.
+```js
+export const selectItems = (state) => state.items;
+export const selectIsLoading = (state) => state.loading;
+```
 
+### Actions
 
 ```js
-export const handleOnMount = (deps) => {
-  () => {
-    // unsubscribe
+export const setLoading = (state, isLoading) => {
+  state.loading = isLoading; // Immer makes this immutable
+};
+
+export const addItem = (state, item) => {
+  state.items.push(item);
+};
+
+export const removeItem = (state, itemId) => {
+  const index = state.items.findIndex(item => item.id === itemId);
+  if (index !== -1) {
+    state.items.splice(index, 1);
   }
-}
+};
+```
 
-export const handleCreateButtonClick = async (e, deps) => {
-  const { store, deps, render } = deps;
-  const formIsVisible = store.selectFormIsVisible();
+## Event Handlers (.handlers.js)
 
-  if (!formIsVisible) {
-    store.setFormIsVisible(true);
-  }
-  deps.render();
-}
+### Special Handlers
 
-export const handleProjectsClick = (e, deps) => {
-  const id = e.target.id
-  console.log('handleProjectsClick', id);
-}
+```js
+// Called when component mounts
+export const handleOnMount = (deps) => {
+  const { store, render } = deps;
+  
+  // Load initial data
+  store.setLoading(true);
+  loadData().then(data => {
+    store.setItems(data);
+    store.setLoading(false);
+    render();
+  });
+
+  // Return cleanup function
+  return () => {
+    // Cleanup code here
+  };
+};
 ```
 
-
-
-* `deps.dispatchEvent` can be used to dispatch custom dom events.
+### Event Handlers
 
 ```js
-export const handleProjectsClick = (e, deps) => {
-  deps.dispatchEvent(new CustomEvent('project-clicked', {
-    projectId: '1',
+export const handleSubmit = async (event, deps) => {
+  const { store, render, attrs, props } = deps;
+  
+  event.preventDefault();
+  
+  const formData = new FormData(event.target);
+  const newItem = Object.fromEntries(formData);
+  
+  store.addItem(newItem);
+  render();
+  
+  // Dispatch custom event
+  deps.dispatchEvent(new CustomEvent('item-added', {
+    detail: { item: newItem }
   }));
-}
-```
-
+};
 
-### Adding additional dependencies
+export const handleItemClick = (event, deps) => {
+  const itemId = event.target.id.replace('item-', '');
+  console.log('Item clicked:', itemId);
+};
+```
 
-This is a simple yet powerful way to do dependency injection. Those are all global singleton dependencies. Technically anything can be injected and be made accessible to all components.
+### Dependency Injection
 
 ```js
+// In your setup.js file
 const componentDependencies = {
-}
-
-const pageDependencies = {
-}
+  apiClient: new ApiClient(),
+  router: new Router()
+};
 
 export const deps = {
   components: componentDependencies,
-  pages: pageDependencies,
-}
+  pages: {}
+};
 ```
 
+Access in handlers:
+```js
+export const handleLoadData = async (event, deps) => {
+  const { apiClient } = deps.components;
+  const data = await apiClient.fetchItems();
+  // ... handle data
+};
+```
 
-## Testing
-
-This framework is written with testability in mind.
-
-
-## View
+## Configuration
 
-Visual testing `rettangoli-vt`
+Create a `rettangoli.config.yaml` file in your project root:
 
+```yaml
+fe:
+  dirs:
+    - "./src/components"
+    - "./src/pages"
+  setup: "setup.js"
+  outfile: "./dist/bundle.js"
+  examples:
+    outputDir: "./vt/specs/examples"
+```
 
-## State Store
+## Testing
 
-Those are all pure functions and it is straighforward to test them. Actions can be turned into pure functions using immer produce.
+### View Components
 
-Example
+Use visual testing with `rtgl vt`:
 
-```yaml
-...
+```bash
+rtgl vt generate
+rtgl vt report
 ```
 
-## Handlers
+## Examples
 
-Test them as normal functions.
-They are not always pure per se due to calling of dependencies. 
+For a complete working example, see the todos app in `examples/example1/`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rettangoli/fe",
-  "version": "0.0.6",
+  "version": "0.0.7-rc2",
   "description": "Frontend framework for building reactive web components",
   "type": "module",
   "main": "./src/index.js",

package/src/cli/watch.js

@@ -8,7 +8,7 @@ import buildRettangoliFrontend from './build.js';
 import { extractCategoryAndComponent } from '../common.js';
 
 
-const setupWatcher = (directory) => {
+const setupWatcher = (directory, options) => {
   watch(
     directory,
     { recursive: true },
@@ -21,7 +21,7 @@ const setupWatcher = (directory) => {
             const { category, component } = extractCategoryAndComponent(filename);
             await writeViewFile(view, category, component);
           }
-          await buildRettangoliFrontend({ dirs: [directory] });
+          await buildRettangoliFrontend(options);
         } catch (error) {
           console.error(`Error processing ${filename}:`, error);
           // Keep the watcher running
@@ -32,7 +32,13 @@ const setupWatcher = (directory) => {
 };
 
 async function startViteServer(options) {
-  const { port = 3001, root = './viz/static' } = options;
+  const { port = 3001, outfile = "./vt/static/main.js" } = options;
+
+  // Extract the directory from outfile path
+  const outDir = path.dirname(outfile);
+  // Go up one level from the JS file directory to serve the site root
+  const root = path.dirname(outDir);
+  console.log('watch root dir:', root)
   try {
     const server = await createServer({
       // any valid user config options, plus `mode` and `configFile`
@@ -53,14 +59,19 @@ async function startViteServer(options) {
 }
 
 
-const startWatching = (options) => {
+const startWatching = async (options) => {
   const { dirs = ['src'], port = 3001 } = options;
 
+  // Do initial build with all directories
+  console.log('Starting initial build...');
+  await buildRettangoliFrontend(options);
+  console.log('Initial build complete');
+
   dirs.forEach(dir => {
-    setupWatcher(dir);
+    setupWatcher(dir, options);
   });
 
-  startViteServer({ port });
+  startViteServer({ port, outfile: options.outfile });
 }
 
 export default startWatching;