@fougere/admin 0.5.0-alpha.0 → 0.6.0-alpha.0

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 (4) hide show
  1. package/dist/provider.d.ts +3 -3
  2. package/dist/provider.js +3 -3
  3. package/package.json +4 -4
  4. package/src/provider.ts +3 -3
package/dist/provider.d.ts CHANGED
@@ -2,12 +2,12 @@
2
2
  * react-admin's `DataProvider`, answered by the Fougere wire.
3
3
  *
4
4
  * Nine functions, and every one of them had a counterpart already: `getList` is
5
- * `ListOptions`, `getManyReference` is the ORM's `findAllByKeys` (written for a
5
+ * `ListOptions`, `getManyReference` is the storage's `findAllByKeys` (written for a
6
6
  * presenter that wanted "the items of these lists"), `filter` is `where` — an
7
7
  * equality map that already refuses an unknown key, because a filter silently
8
8
  * dropped had once returned the whole table.
9
9
  *
10
- * It talks to the FAÇADE and never to an ORM, which is not a precaution here but a
10
+ * It talks to the FAÇADE and never to a storage, which is not a precaution here but a
11
11
  * consequence: this runs in a browser, and the only thing a browser can reach is the
12
12
  * call endpoint. Judges, presenters and middlewares are therefore on the path of
13
13
  * every read and every write the back-office makes.
@@ -68,7 +68,7 @@ export declare function createDataProvider(options: ProviderOptions): {
68
68
  data: Row;
69
69
  }>;
70
70
  /**
71
- * N calls, and the reason is upstream: `findByKeys` is a gesture of the ORM port,
71
+ * N calls, and the reason is upstream: `findByKeys` is a gesture of the storage port,
72
72
  * not one of `Crud`'s five ops, so there is no door to ask for several rows by id.
73
73
  * Said here rather than hidden — the day `Crud` names that op this becomes one call.
74
74
  */
package/dist/provider.js CHANGED
@@ -2,12 +2,12 @@
2
2
  * react-admin's `DataProvider`, answered by the Fougere wire.
3
3
  *
4
4
  * Nine functions, and every one of them had a counterpart already: `getList` is
5
- * `ListOptions`, `getManyReference` is the ORM's `findAllByKeys` (written for a
5
+ * `ListOptions`, `getManyReference` is the storage's `findAllByKeys` (written for a
6
6
  * presenter that wanted "the items of these lists"), `filter` is `where` — an
7
7
  * equality map that already refuses an unknown key, because a filter silently
8
8
  * dropped had once returned the whole table.
9
9
  *
10
- * It talks to the FAÇADE and never to an ORM, which is not a precaution here but a
10
+ * It talks to the FAÇADE and never to a storage, which is not a precaution here but a
11
11
  * consequence: this runs in a browser, and the only thing a browser can reach is the
12
12
  * call endpoint. Judges, presenters and middlewares are therefore on the path of
13
13
  * every read and every write the back-office makes.
@@ -103,7 +103,7 @@ export function createDataProvider(options) {
103
103
  return { data: row };
104
104
  },
105
105
  /**
106
- * N calls, and the reason is upstream: `findByKeys` is a gesture of the ORM port,
106
+ * N calls, and the reason is upstream: `findByKeys` is a gesture of the storage port,
107
107
  * not one of `Crud`'s five ops, so there is no door to ask for several rows by id.
108
108
  * Said here rather than hidden — the day `Crud` names that op this becomes one call.
109
109
  */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fougere/admin",
3
- "version": "0.5.0-alpha.0",
3
+ "version": "0.6.0-alpha.0",
4
4
  "description": "A back-office derived from what the app already says it hosts — a react-admin DataProvider over the Fougere wire.",
5
5
  "keywords": [
6
6
  "fougere",
@@ -34,9 +34,9 @@
34
34
  "src"
35
35
  ],
36
36
  "dependencies": {
37
- "@fougere/core": "0.5.0-alpha.0",
38
- "@fougere/app": "0.5.0-alpha.0",
39
- "@fougere/schema": "0.5.0-alpha.0"
37
+ "@fougere/app": "1.0.0",
38
+ "@fougere/core": "0.6.0-alpha.0",
39
+ "@fougere/schema": "0.6.0-alpha.0"
40
40
  },
41
41
  "devDependencies": {
42
42
  "@mui/material": "^9.3.1",
package/src/provider.ts CHANGED
@@ -2,12 +2,12 @@
2
2
  * react-admin's `DataProvider`, answered by the Fougere wire.
3
3
  *
4
4
  * Nine functions, and every one of them had a counterpart already: `getList` is
5
- * `ListOptions`, `getManyReference` is the ORM's `findAllByKeys` (written for a
5
+ * `ListOptions`, `getManyReference` is the storage's `findAllByKeys` (written for a
6
6
  * presenter that wanted "the items of these lists"), `filter` is `where` — an
7
7
  * equality map that already refuses an unknown key, because a filter silently
8
8
  * dropped had once returned the whole table.
9
9
  *
10
- * It talks to the FAÇADE and never to an ORM, which is not a precaution here but a
10
+ * It talks to the FAÇADE and never to a storage, which is not a precaution here but a
11
11
  * consequence: this runs in a browser, and the only thing a browser can reach is the
12
12
  * call endpoint. Judges, presenters and middlewares are therefore on the path of
13
13
  * every read and every write the back-office makes.
@@ -147,7 +147,7 @@ export function createDataProvider(options: ProviderOptions) {
147
147
  },
148
148
 
149
149
  /**
150
- * N calls, and the reason is upstream: `findByKeys` is a gesture of the ORM port,
150
+ * N calls, and the reason is upstream: `findByKeys` is a gesture of the storage port,
151
151
  * not one of `Crud`'s five ops, so there is no door to ask for several rows by id.
152
152
  * Said here rather than hidden — the day `Crud` names that op this becomes one call.
153
153
  */