@ferrflow/doc 7.21.1 → 7.21.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.
- package/data/benchmarks.json +698 -698
- package/docs-en/reference/errors.md +20 -0
- package/docs-fr/reference/errors.md +20 -0
- package/package.json +1 -1
|
@@ -121,6 +121,26 @@ More than one config file was found in the project root (e.g. both `ferrflow.jso
|
|
|
121
121
|
|
|
122
122
|
Running `ferrflow init` when a config file already exists.
|
|
123
123
|
|
|
124
|
+
### E1024: Versioned file does not exist
|
|
125
|
+
|
|
126
|
+
<span id="e1024"></span>
|
|
127
|
+
|
|
128
|
+
A package that this run would release lists a `versionedFiles` entry whose file is not on disk. The run stops at plan time rather than at write time, where the same problem surfaces as a bare read error.
|
|
129
|
+
|
|
130
|
+
The usual cause is a path written relative to the package instead of the repository root. `package.path` is not a prefix that FerrFlow adds for you:
|
|
131
|
+
|
|
132
|
+
```toml
|
|
133
|
+
[[package]]
|
|
134
|
+
name = "api"
|
|
135
|
+
path = "packages/api"
|
|
136
|
+
|
|
137
|
+
[[package.versioned_files]]
|
|
138
|
+
path = "Cargo.toml" # wrong, looked up at the repository root
|
|
139
|
+
# path = "packages/api/Cargo.toml" # right
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
The error names the path it probably meant. `ferrflow validate` reports the same problem for every configured package, including ones this run would not touch.
|
|
143
|
+
|
|
124
144
|
## Validation Errors
|
|
125
145
|
|
|
126
146
|
### E1100: Invalid repo spec
|
|
@@ -121,6 +121,26 @@ Plusieurs fichiers de config trouv\u00e9s dans le r\u00e9pertoire.
|
|
|
121
121
|
|
|
122
122
|
`ferrflow init` lanc\u00e9 alors qu'un fichier de config existe d\u00e9j\u00e0.
|
|
123
123
|
|
|
124
|
+
### E1024 : Fichier versionne introuvable
|
|
125
|
+
|
|
126
|
+
<span id="e1024"></span>
|
|
127
|
+
|
|
128
|
+
Un package que cette execution allait publier declare une entree `versionedFiles` dont le fichier n'est pas sur le disque. L'execution s'arrete au moment du plan plutot qu'au moment de l'ecriture, ou le meme probleme apparait sous la forme d'une simple erreur de lecture.
|
|
129
|
+
|
|
130
|
+
La cause habituelle est un chemin ecrit relativement au package plutot qu'a la racine du depot. `package.path` n'est pas un prefixe que FerrFlow ajoute pour vous :
|
|
131
|
+
|
|
132
|
+
```toml
|
|
133
|
+
[[package]]
|
|
134
|
+
name = "api"
|
|
135
|
+
path = "packages/api"
|
|
136
|
+
|
|
137
|
+
[[package.versioned_files]]
|
|
138
|
+
path = "Cargo.toml" # faux, cherche a la racine du depot
|
|
139
|
+
# path = "packages/api/Cargo.toml" # correct
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
L'erreur indique le chemin qu'elle suppose correct. `ferrflow validate` signale le meme probleme pour tous les packages configures, y compris ceux que cette execution n'aurait pas touches.
|
|
143
|
+
|
|
124
144
|
## Erreurs de validation
|
|
125
145
|
|
|
126
146
|
### E1100 : Spec de repo invalide
|