You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: templates/ads-b-frontend/AGENTS.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,10 +64,10 @@ Use `moose --help` to discover all commands. Most useful for getting context:
64
64
65
65
### Adding a data model
66
66
67
-
MooseStack's core pattern: define a TypeScript interface once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
67
+
MooseStack's core pattern: define a TypeScript interface once, then configure an `IngestPipeline` to create your data pipeline.
@@ -98,6 +92,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
98
92
99
93
-**DO** use `orderByFields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
100
94
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
101
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
95
+
-**DO** use `IngestPipeline` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
102
96
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
103
-
-**DO** export new primitives from your app's entry file. **DON'T** forget to export — MooseStack won't discover unexported primitives.
97
+
-**DO** export new primitives from your app's entry file (`app/index.ts`). **DON'T** forget to export — MooseStack won't discover unexported primitives.
Copy file name to clipboardExpand all lines: templates/ads-b/AGENTS.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,10 +60,10 @@ Use `moose --help` to discover all commands. Most useful for getting context:
60
60
61
61
### Adding a data model
62
62
63
-
MooseStack's core pattern: define a TypeScript interface once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
63
+
MooseStack's core pattern: define a TypeScript interface once, then configure an `IngestPipeline` to create your data pipeline.
@@ -94,6 +88,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
94
88
95
89
-**DO** use `orderByFields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
96
90
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
97
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
91
+
-**DO** use `IngestPipeline` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
98
92
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
99
-
-**DO** export new primitives from your app's entry file. **DON'T** forget to export — MooseStack won't discover unexported primitives.
93
+
-**DO** export new primitives from your app's entry file (`app/index.ts`). **DON'T** forget to export — MooseStack won't discover unexported primitives.
Copy file name to clipboardExpand all lines: templates/brainwaves/AGENTS.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,10 +63,10 @@ Use `moose --help` to discover all commands. Most useful for getting context:
63
63
64
64
### Adding a data model
65
65
66
-
MooseStack's core pattern: define a TypeScript interface once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
66
+
MooseStack's core pattern: define a TypeScript interface once, then configure an `IngestPipeline` to create your data pipeline.
@@ -97,6 +91,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
97
91
98
92
-**DO** use `orderByFields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
99
93
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
100
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
94
+
-**DO** use `IngestPipeline` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
101
95
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
102
-
-**DO** export new primitives from your app's entry file. **DON'T** forget to export — MooseStack won't discover unexported primitives.
96
+
-**DO** export new primitives from your app's entry file (`app/index.ts`). **DON'T** forget to export — MooseStack won't discover unexported primitives.
Copy file name to clipboardExpand all lines: templates/github-dev-trends/AGENTS.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,10 +66,10 @@ Use `moose --help` to discover all commands. Most useful for getting context:
66
66
67
67
### Adding a data model
68
68
69
-
MooseStack's core pattern: define a TypeScript interface once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
69
+
MooseStack's core pattern: define a TypeScript interface once, then configure an `IngestPipeline` to create your data pipeline.
@@ -100,6 +94,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
100
94
101
95
-**DO** use `orderByFields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
102
96
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
103
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
97
+
-**DO** use `IngestPipeline` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
104
98
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
105
-
-**DO** export new primitives from your app's entry file. **DON'T** forget to export — MooseStack won't discover unexported primitives.
99
+
-**DO** export new primitives from your app's entry file (`app/index.ts`). **DON'T** forget to export — MooseStack won't discover unexported primitives.
Copy file name to clipboardExpand all lines: templates/live-heartrate-leaderboard/AGENTS.md
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,24 +67,28 @@ Use `moose --help` to discover all commands. Most useful for getting context:
67
67
68
68
### Adding a data model
69
69
70
-
MooseStack's core pattern: define a Python dataclass once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
70
+
MooseStack's core pattern: define a Pydantic model once, then configure an `IngestPipeline` to create your data pipeline.
71
71
72
72
```python
73
-
from moose_lib importOlapTable, Stream, IngestApi
74
-
fromdataclassesimportdataclass
73
+
from moose_lib importIngestPipeline, IngestPipelineConfig
Use `order_by_fields` to control ClickHouse table ordering — put your most-filtered columns first. Use the ClickHouse Best Practices Skill to choose the right ordering.
@@ -95,6 +99,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
95
99
96
100
-**DO** use `order_by_fields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
97
101
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
98
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
102
+
-**DO** use `IngestPipeline` with `IngestPipelineConfig` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
99
103
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
100
-
-**DO**export new primitives from your app's entry file.**DON'T**forget to export — MooseStack won't discover unexported primitives.
104
+
-**DO**import new primitives in your app's `main.py`.**DON'T**leave modules unimported — MooseStack discovers primitives by loading `main.py`, so unimported modules won't be found.
Copy file name to clipboardExpand all lines: templates/next-app-empty/AGENTS.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,10 +63,10 @@ Use `moose --help` to discover all commands. Most useful for getting context:
63
63
64
64
### Adding a data model
65
65
66
-
MooseStack's core pattern: define a TypeScript interface once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
66
+
MooseStack's core pattern: define a TypeScript interface once, then configure an `IngestPipeline` to create your data pipeline.
@@ -97,6 +91,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
97
91
98
92
-**DO** use `orderByFields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
99
93
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
100
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
94
+
-**DO** use `IngestPipeline` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
101
95
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
102
-
-**DO** export new primitives from your app's entry file. **DON'T** forget to export — MooseStack won't discover unexported primitives.
96
+
-**DO** export new primitives from your app's entry file (`app/index.ts`). **DON'T** forget to export — MooseStack won't discover unexported primitives.
Copy file name to clipboardExpand all lines: templates/python-empty/AGENTS.md
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,24 +57,28 @@ Use `moose --help` to discover all commands. Most useful for getting context:
57
57
58
58
### Adding a data model
59
59
60
-
MooseStack's core pattern: define a Python dataclass once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
60
+
MooseStack's core pattern: define a Pydantic model once, then configure an `IngestPipeline` to create your data pipeline.
61
61
62
62
```python
63
-
from moose_lib importOlapTable, Stream, IngestApi
64
-
fromdataclassesimportdataclass
63
+
from moose_lib importIngestPipeline, IngestPipelineConfig
Use `order_by_fields` to control ClickHouse table ordering — put your most-filtered columns first. Use the ClickHouse Best Practices Skill to choose the right ordering.
@@ -85,6 +89,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
85
89
86
90
-**DO** use `order_by_fields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
87
91
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
88
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
92
+
-**DO** use `IngestPipeline` with `IngestPipelineConfig` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
89
93
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
90
-
-**DO**export new primitives from your app's entry file.**DON'T**forget to export — MooseStack won't discover unexported primitives.
94
+
-**DO**import new primitives in your app's `main.py`.**DON'T**leave modules unimported — MooseStack discovers primitives by loading `main.py`, so unimported modules won't be found.
Copy file name to clipboardExpand all lines: templates/python-experimental/AGENTS.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Ports used: 4000, 5001, 7233, 8080, 9000, 18123. See `moose.config.toml` to chan
12
12
13
13
| File | Purpose |
14
14
| --- | --- |
15
-
|`app/ingest/models.py`| Data models (dataclasses + pipeline declarations) |
15
+
|`app/ingest/models.py`| Data models (Pydantic models + pipeline declarations) |
16
16
|`moose.config.toml`| Port and service configuration |
17
17
18
18
## Dev Environment
@@ -58,24 +58,28 @@ Use `moose --help` to discover all commands. Most useful for getting context:
58
58
59
59
### Adding a data model
60
60
61
-
MooseStack's core pattern: define a Python dataclass once, then wire up individual primitives (`OlapTable`, `Stream`, `IngestApi`) to create your data pipeline.
61
+
MooseStack's core pattern: define a Pydantic model once, then configure an `IngestPipeline` to create your data pipeline.
62
62
63
63
```python
64
-
from moose_lib importOlapTable, Stream, IngestApi
65
-
fromdataclassesimportdataclass
64
+
from moose_lib importIngestPipeline, IngestPipelineConfig
Use `order_by_fields` to control ClickHouse table ordering — put your most-filtered columns first. Use the ClickHouse Best Practices Skill to choose the right ordering.
@@ -86,6 +90,6 @@ For advanced table configuration (engines, indexes, projections), see `moose doc
86
90
87
91
-**DO** use `order_by_fields` to define ClickHouse table ordering. **DON'T** rely on default ordering — always specify based on query patterns.
88
92
-**DO** use `currentDatabase()` in SQL queries. **DON'T** hardcode the database name.
89
-
-**DO** use `OlapTable` + `Stream` + `IngestApi` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
93
+
-**DO** use `IngestPipeline` with `IngestPipelineConfig` for new data models. **DON'T** write raw CREATE TABLE DDL — MooseStack generates tables from your models.
90
94
-**DO** use the ClickHouse Best Practices Skill for schema decisions. **DON'T** guess at ClickHouse data types or engine choices.
91
-
-**DO**export new primitives from your app's entry file.**DON'T**forget to export — MooseStack won't discover unexported primitives.
95
+
-**DO**import new primitives in your app's `main.py`.**DON'T**leave modules unimported — MooseStack discovers primitives by loading `main.py`, so unimported modules won't be found.
0 commit comments