🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more →
plain-forge
Advanced tools
plain-forge - npm Package Compare versions
@@ -77,4 +77,3 @@ --- | ||
| ***acceptance tests*** | ||
| - Sending a :Message: to a :Conversation: with three participants should | ||
| make the message visible to all three. | ||
| - Sending a :Message: to a :Conversation: with three participants should make the message visible to all three. | ||
| ``` |
@@ -17,4 +17,4 @@ --- | ||
| 3. **A binary file.** PNG, JPG, GIF, PDF, DOCX, XLSX, ZIP, MP3, MP4, compiled binaries (`.exe`, `.so`, `.class`, `.wasm`), and anything else that isn't human-readable text in its raw form. Binary content cannot be meaningfully consumed by the renderer — transcribe it into a text-based form first (a UI screenshot becomes a Markdown description, a PDF spec becomes a Markdown extract or the underlying JSON Schema / OpenAPI, an architecture diagram becomes a Mermaid block). | ||
| 4. **Another `.plain` file.** `[Auth Module](auth.plain)` is invalid. To reference another module, use the `require` or `import` frontmatter directives. Do not link it as a markdown resource; the `plain-dry-run` will flag this as a syntax error. | ||
| If the markdown-link target ends with `/`, contains `://`, resolves to a directory, or has a binary extension, **stop** — it cannot be a linked resource. Convert it first. | ||
@@ -35,11 +35,11 @@ ## URLs and folder paths must not appear *anywhere* in `.plain` content | ||
| - :TaskCreateRequest: is the JSON payload for creating a task, defined by | ||
| [resources/task_create_request.schema.json](resources/task_create_request.schema.json). | ||
| - :TasksAPI: is the public HTTP surface for tasks, defined by | ||
| [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml). | ||
| - :TaskCreateRequest: is the JSON payload for creating a task. | ||
| - It is defined by [resources/task_create_request.schema.json](resources/task_create_request.schema.json). | ||
| - :TasksAPI: is the public HTTP surface for tasks. | ||
| - It is defined by [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml). | ||
| ***functional specs*** | ||
| - :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the | ||
| `POST /tasks` endpoint of :TasksAPI:. The endpoint responds per :TasksAPI:. | ||
| - :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the `POST /tasks` endpoint of :TasksAPI:. | ||
| - The endpoint responds per :TasksAPI:. | ||
| ``` | ||
@@ -55,4 +55,4 @@ | ||
| - :TaskModalSpec: is the user-interface contract for the task modal, | ||
| fully described in [task_modal_specification.yaml](task_modal_specification.yaml). | ||
| - :TaskModalSpec: is the user-interface contract for the task modal. | ||
| - It is fully described in [task_modal_specification.yaml](task_modal_specification.yaml). | ||
@@ -59,0 +59,0 @@ ***functional specs*** |
@@ -29,13 +29,12 @@ --- | ||
| ***definitions*** | ||
| - :AuthData: is the authentication data structure. Its format is defined | ||
| in the [auth schema](resources/auth_schema.json). | ||
| - :AuthData: is the authentication data structure. | ||
| - Its format is defined in the [auth schema](resources/auth_schema.json). | ||
| ***implementation reqs*** | ||
| - When transforming :BackupData:, use the JOLT transform defined in | ||
| [backup_transform.jolt](resources/backup_transform.jolt). | ||
| - When transforming :BackupData:, use the JOLT transform. | ||
| - The transform is defined in [backup_transform.jolt](resources/backup_transform.jolt). | ||
| ***functional specs*** | ||
| - The system should expose an API conforming to the | ||
| [API specification](resources/api_spec.yaml). | ||
| - The system should expose an API conforming to the [API specification](resources/api_spec.yaml). | ||
| ``` | ||
@@ -42,0 +41,0 @@ |
@@ -72,6 +72,5 @@ --- | ||
| - The system should process standard :Order: by validating and storing it. | ||
| - The system should process express :Order: by queuing it for immediate dispatch | ||
| without validation. | ||
| - The system should process bulk :Order: by splitting it into sub-orders of 100 | ||
| items each and processing them individually. | ||
| - The system should process express :Order: by queuing it for immediate dispatch without validation. | ||
| - The system should process bulk :Order: by splitting it into sub-orders of 100 items each. | ||
| - Each sub-order is processed individually. | ||
| ``` | ||
@@ -92,4 +91,3 @@ | ||
| - The system should paginate when fetching :Resource: items from the external API. | ||
| - The system should retry fetching :Resource: on transient errors using | ||
| exponential backoff. | ||
| - The system should retry fetching :Resource: on transient errors using exponential backoff. | ||
| ``` | ||
@@ -96,0 +94,0 @@ |
@@ -114,6 +114,6 @@ --- | ||
| - The system should generate a standard :MealPlan: using round-robin :Recipe: assignment. | ||
| - The system should generate a restrictive :MealPlan: by filtering out excluded | ||
| :Ingredient: items before applying round-robin assignment. | ||
| - The system should allow :User: to manually assign :Recipe: items to individual | ||
| :Slot: items for a custom :MealPlan:. | ||
| - The system should generate a restrictive :MealPlan:. | ||
| - Excluded :Ingredient: items are filtered out first. | ||
| - Round-robin :Recipe: assignment is then applied. | ||
| - The system should allow :User: to manually assign :Recipe: items to :Slot: items for a custom :MealPlan:. | ||
| ``` | ||
@@ -120,0 +120,0 @@ |
@@ -187,4 +187,4 @@ --- | ||
| ```plain | ||
| - :User: should be able to add :Task:. The details of the user interface | ||
| are provided in the file [task_modal_specification.yaml](task_modal_specification.yaml). | ||
| - :User: should be able to add :Task:. | ||
| - The user-interface details are in [task_modal_specification.yaml](task_modal_specification.yaml). | ||
| ``` | ||
@@ -224,11 +224,11 @@ | ||
| - :TaskCreateRequest: is the JSON payload for creating a task, defined by | ||
| [resources/task_create_request.schema.json](resources/task_create_request.schema.json). | ||
| - :TasksAPI: is the public HTTP surface for tasks, defined by | ||
| [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml). | ||
| - :TaskCreateRequest: is the JSON payload for creating a task. | ||
| - It is defined by [resources/task_create_request.schema.json](resources/task_create_request.schema.json). | ||
| - :TasksAPI: is the public HTTP surface for tasks. | ||
| - It is defined by [resources/tasks_openapi.yaml](resources/tasks_openapi.yaml). | ||
| ***functional specs*** | ||
| - :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the | ||
| `POST /tasks` endpoint of :TasksAPI:. The endpoint responds per :TasksAPI:. | ||
| - :User: should be able to add :Task: by POSTing :TaskCreateRequest: to the `POST /tasks` endpoint of :TasksAPI:. | ||
| - The endpoint responds per :TasksAPI:. | ||
| ``` | ||
@@ -248,4 +248,4 @@ | ||
| - :TaskModalSpec: is the user-interface contract for the task modal, | ||
| fully described in [task_modal_specification.yaml](task_modal_specification.yaml). | ||
| - :TaskModalSpec: is the user-interface contract for the task modal. | ||
| - It is fully described in [task_modal_specification.yaml](task_modal_specification.yaml). | ||
@@ -252,0 +252,0 @@ ***functional specs*** |
+1
-1
| { | ||
| "name": "plain-forge", | ||
| "version": "1.0.14", | ||
| "version": "1.0.15", | ||
| "description": "Conversational spec-writing tool for ***plain specification language", | ||
@@ -5,0 +5,0 @@ "type": "module", |
New alerts
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Found 1 instance in 1 package
Fixed alerts
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
621383
0.02%No dependency changes