Skip to content

Commit 3a2caff

Browse files
committed
Implement Kanban component and update related documentation; refine example schemas for better clarity
1 parent c4a6443 commit 3a2caff

5 files changed

Lines changed: 1280 additions & 5 deletions

File tree

.github/copilot-instructions.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,4 +143,28 @@ export const InputRenderer = ({ schema, value, onChange }: Props) => {
143143
)}
144144
</div>
145145
);
146-
};
146+
};
147+
148+
```
149+
150+
---
151+
152+
## 6. AI Workflow Instructions
153+
154+
### 🟢 On "Create New Component":
155+
156+
1. **Define Protocol:** Create `interface XSchema` in `@object-ui/types`.
157+
2. **Implement UI:** Create `XRenderer` in `@object-ui/components` using Shadcn primitives.
158+
3. **Register:** Add to the default component registry.
159+
4. **Standalone Check:** Ask yourself: *"Can a user use this component with a static JSON array?"* If no, refactor data logic to `DataSource`.
160+
161+
### 🟡 On "Data Fetching Logic":
162+
163+
1. **Abstraction:** Never import `axios` or `fetch` directly in a UI component.
164+
2. **Hook:** Use `useDataSource()` or `useDataScope()` to request data.
165+
3. **Example:** For an Autocomplete, call `dataSource.find({ search: term })`, allowing the user to inject *any* data source (REST API, Algolia, or local array).
166+
167+
### 🟣 On "Promoting the Project":
168+
169+
1. **Keywords:** Focus on "Tailwind-Native", "Headless", "Shadcn Compatible".
170+
2. **Differentiation:** Emphasize that unlike other low-code renderers, Object UI allows full styling control via standard Tailwind classes.

0 commit comments

Comments
 (0)