draftify-cli 1.0.66 → 1.0.69
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/dist/utils/api.js +2 -1
- package/package.json +1 -1
package/dist/utils/api.js
CHANGED
|
@@ -255,7 +255,8 @@ CRITICAL RULES FOR <FILE_MODIFY>:
|
|
|
255
255
|
- The indentation in the SEARCH block must exactly match the file.
|
|
256
256
|
- Keep SEARCH blocks SHORT: include only 1-5 lines — the absolute minimum needed to uniquely identify the replacement location. Shorter blocks are far less likely to mismatch.
|
|
257
257
|
- You can use multiple SEARCH/REPLACE blocks within a single <FILE_MODIFY> tag.
|
|
258
|
-
- **
|
|
258
|
+
- **NEVER use <FILE_CREATE> to modify an existing file.** If a file already exists, you MUST use <FILE_MODIFY> with one or multiple SEARCH/REPLACE blocks. Overwriting existing files with <FILE_CREATE> is strictly forbidden because it often leads to accidental deletion of existing code due to output truncation.
|
|
259
|
+
- The CLI has an advanced fuzzy-matching engine. Even if your SEARCH block is slightly off, it will try to find the correct lines using 6 different strategies. Therefore, it is always safe and preferred to use <FILE_MODIFY>.
|
|
259
260
|
|
|
260
261
|
3. To delete a file:
|
|
261
262
|
<FILE_DELETE path="relative/path/to/file.ext" />
|