@akanjs/cli 0.9.58-canary.2 → 0.9.58-canary.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (8) hide show
  1. package/cjs/src/guidelines/sharedUiUsage/sharedUiUsage.instruction.md +0 -3
  2. package/cjs/src/templates/module/__model__.dictionary.js +0 -1
  3. package/cjs/src/templates/module/__model__.document.js +1 -1
  4. package/esm/src/guidelines/sharedUiUsage/sharedUiUsage.instruction.md +0 -3
  5. package/esm/src/templates/module/__model__.dictionary.js +0 -1
  6. package/esm/src/templates/module/__model__.document.js +1 -1
  7. package/package.json +1 -1
  8. package/src/guidelines/sharedUiUsage/sharedUiUsage.instruction.md +0 -3
package/cjs/src/guidelines/sharedUiUsage/sharedUiUsage.instruction.md CHANGED
@@ -88,8 +88,6 @@ const MyComponent = () => {
88
88
  value={formState.status}
89
89
  items={cnst.Status}
90
90
  onChange={(status) => st.do.setStatusOnMyModel(status)}
91
- model="myModel"
92
- field="status"
93
91
  />
94
92
  </>
95
93
  );
@@ -280,7 +278,6 @@ Components seamlessly integrate with the state management:
280
278
  ## Best Practices
281
279
 
282
280
  1. **Use the appropriate component type** for each part of your feature:
283
-
284
281
  - Use **Field** components for data entry
285
282
  - Use **Data** components for data visualization and management
286
283
  - Use **Load** components for data fetching
package/cjs/src/templates/module/__model__.dictionary.js CHANGED
@@ -38,7 +38,6 @@ export const dictionary = modelDictionary(["en", "ko"])
38
38
  field: t(["Field", "\uD544\uB4DC"]).desc(["Field description", "\uD544\uB4DC \uC124\uBA85"]),
39
39
  }))
40
40
  .insight<${dict.Model}Insight>((t) => ({}))
41
- .query<${dict.Model}Filter>((fn) => ({}))
42
41
  .slice<${dict.Model}Slice>((fn) => ({
43
42
  inPublic: fn(["${dict.Model} In Public", "${dict.Model} \uACF5\uAC1C"]).arg((t) => ({})),
44
43
  }))
package/cjs/src/templates/module/__model__.document.js CHANGED
@@ -35,7 +35,7 @@ export class ${dict.Model}Filter extends from(cnst.${dict.Model}, (filter) => ({
35
35
 
36
36
  export class ${dict.Model} extends by(cnst.${dict.Model}) {}
37
37
 
38
- export class ${dict.Model}Model extends into(${dict.Model}, ${dict.Model}Filter, cnst.${dict.model}) {}
38
+ export class ${dict.Model}Model extends into(${dict.Model}, ${dict.Model}Filter, cnst.${dict.model}, () => ({})) {}
39
39
 
40
40
  export class ${dict.Model}Middleware extends beyond(${dict.Model}Model, ${dict.Model}) {
41
41
  onSchema(schema: SchemaOf<${dict.Model}Model, ${dict.Model}>) {
package/esm/src/guidelines/sharedUiUsage/sharedUiUsage.instruction.md CHANGED
@@ -88,8 +88,6 @@ const MyComponent = () => {
88
88
  value={formState.status}
89
89
  items={cnst.Status}
90
90
  onChange={(status) => st.do.setStatusOnMyModel(status)}
91
- model="myModel"
92
- field="status"
93
91
  />
94
92
  </>
95
93
  );
@@ -280,7 +278,6 @@ Components seamlessly integrate with the state management:
280
278
  ## Best Practices
281
279
 
282
280
  1. **Use the appropriate component type** for each part of your feature:
283
-
284
281
  - Use **Field** components for data entry
285
282
  - Use **Data** components for data visualization and management
286
283
  - Use **Load** components for data fetching
package/esm/src/templates/module/__model__.dictionary.js CHANGED
@@ -15,7 +15,6 @@ export const dictionary = modelDictionary(["en", "ko"])
15
15
  field: t(["Field", "\uD544\uB4DC"]).desc(["Field description", "\uD544\uB4DC \uC124\uBA85"]),
16
16
  }))
17
17
  .insight<${dict.Model}Insight>((t) => ({}))
18
- .query<${dict.Model}Filter>((fn) => ({}))
19
18
  .slice<${dict.Model}Slice>((fn) => ({
20
19
  inPublic: fn(["${dict.Model} In Public", "${dict.Model} \uACF5\uAC1C"]).arg((t) => ({})),
21
20
  }))
package/esm/src/templates/module/__model__.document.js CHANGED
@@ -12,7 +12,7 @@ export class ${dict.Model}Filter extends from(cnst.${dict.Model}, (filter) => ({
12
12
 
13
13
  export class ${dict.Model} extends by(cnst.${dict.Model}) {}
14
14
 
15
- export class ${dict.Model}Model extends into(${dict.Model}, ${dict.Model}Filter, cnst.${dict.model}) {}
15
+ export class ${dict.Model}Model extends into(${dict.Model}, ${dict.Model}Filter, cnst.${dict.model}, () => ({})) {}
16
16
 
17
17
  export class ${dict.Model}Middleware extends beyond(${dict.Model}Model, ${dict.Model}) {
18
18
  onSchema(schema: SchemaOf<${dict.Model}Model, ${dict.Model}>) {
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "type": "module",
3
3
  "sourceType": "module",
4
4
  "name": "@akanjs/cli",
5
- "version": "0.9.58-canary.2",
5
+ "version": "0.9.58-canary.3",
6
6
  "bin": {
7
7
  "akan": "esm/index.js"
8
8
  },
package/src/guidelines/sharedUiUsage/sharedUiUsage.instruction.md CHANGED
@@ -88,8 +88,6 @@ const MyComponent = () => {
88
88
  value={formState.status}
89
89
  items={cnst.Status}
90
90
  onChange={(status) => st.do.setStatusOnMyModel(status)}
91
- model="myModel"
92
- field="status"
93
91
  />
94
92
  </>
95
93
  );
@@ -280,7 +278,6 @@ Components seamlessly integrate with the state management:
280
278
  ## Best Practices
281
279
 
282
280
  1. **Use the appropriate component type** for each part of your feature:
283
-
284
281
  - Use **Field** components for data entry
285
282
  - Use **Data** components for data visualization and management
286
283
  - Use **Load** components for data fetching