@formancy/code-style 0.12.0 → 0.13.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.
package/README.md CHANGED
@@ -94,10 +94,10 @@ configuration.
94
94
  ## Where it comes from
95
95
 
96
96
  The module and its test, `src/code-style.mjs` and `src/code-style.test.mjs`,
97
- were written for Formancy Health (formancy.ai-health 0017) and are carried here
98
- byte for byte; the repositories that copied them pin this package in their place
99
- once it is released. The test is this package's suite. It lints a repository of
100
- its own, written to the system's temporary directory, and holds that each rule
97
+ were written for Formancy Health (formancy.ai-health 0017) and moved here.
98
+ Formancy Health and Formancy Data, which carried copies, pin this package exactly
99
+ from 0.12.0, so a rule is changed here and reaches them by a release. The test is
100
+ this package's suite. It lints a repository of its own, written to the system's temporary directory, and holds that each rule
101
101
  runs at error on the kind of file it is for and that each path does what it
102
102
  says. It does not hold that what a rule reports is a defect.
103
103
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@formancy/code-style",
3
- "version": "0.12.0",
3
+ "version": "0.13.0",
4
4
  "description": "The ESLint rules and the Prettier format the formancy repositories share: one module, which each repository calls with its own paths.",
5
5
  "license": "Apache-2.0",
6
6
  "type": "module",
@@ -16,8 +16,8 @@
16
16
  "//check:pkg": [
17
17
  "publint only, as for @formancy/themes: this package ships one JavaScript module",
18
18
  "and no types, so there is nothing for attw to resolve. Nothing here builds or",
19
- "type-checks either: the module is published as it is written, byte for byte the",
20
- "copy formancy.ai-health and formancy.ai-data carry until they pin this package."
19
+ "type-checks either: the module is published as it is written, and the formancy",
20
+ "repositories that once carried copies of it pin this package exactly."
21
21
  ],
22
22
  "dependencies": {
23
23
  "@eslint-community/eslint-plugin-eslint-comments": "^4.8.1",
@@ -7,12 +7,14 @@ import { isAbsolute, resolve } from 'node:path'
7
7
  import tseslint from 'typescript-eslint'
8
8
 
9
9
  /**
10
- * The lint rules and the format the four formancy repositories share: what
11
- * formancy.ai will publish as `@formancy/code-style`, and until then this
12
- * file, copied byte for byte into each repository, which calls it with its
13
- * own paths and pins the package in its place once it is released
14
- * (formancy.ai-health 0017). Nothing here names a path of one repository;
15
- * a reason that holds for one alone is written where that one calls it.
10
+ * The lint rules and the format the formancy repositories share, published
11
+ * by formancy.ai as `@formancy/code-style`: formancy.ai lints itself with
12
+ * it from its workspace, and Formancy Health and Formancy Data pin a
13
+ * release exactly. Each calls it with its own paths. Written for Formancy
14
+ * Health (formancy.ai-health 0017) and moved here, where a rule is now
15
+ * changed, reaching the others by a release and a bump of each pin. Nothing
16
+ * here names a path of one repository; a reason that holds for one alone is
17
+ * written where that one calls it.
16
18
  *
17
19
  * The rules are @eslint/js's recommended set and typescript-eslint's
18
20
  * type-aware one, every rule `error` or `off`: a warning is a finding