@plutoframework/frontend 0.1.2 → 0.1.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/README.md +7 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -206,3 +206,10 @@ Braces, multiline blocks, separated object/type fields and logical blank lines
|
|
|
206
206
|
are enforced; nested ternaries require explicit branches or named mappings.
|
|
207
207
|
The policy is visible in `scripts/readability.mjs`. These are dev-only tools and
|
|
208
208
|
add no runtime dependencies to state or React entrypoints.
|
|
209
|
+
|
|
210
|
+
Standalone comment blocks have one blank line above them, except at line 1.
|
|
211
|
+
Consecutive comment lines stay together, and the comment remains attached to the
|
|
212
|
+
code below. JavaScript and TypeScript lint/format checks enforce this convention,
|
|
213
|
+
including the start of a function or branch. Inline trailing comments are kept
|
|
214
|
+
in place, and next-line compiler/linter directives retain their target. The
|
|
215
|
+
cross-language convention is also recorded in AGENTS.md for future changes.
|