@palbase/backend 10.0.0 → 10.2.0

package/docs/config.md

@@ -84,11 +84,17 @@ export default defineFlags({
     new_checkout: flag({ type: "boolean", default: false, description: "Gate the redesigned checkout" }),
     upload_limit: flag({ type: "number", default: 10 }),
     theme:        flag({ type: "string", default: "system", variants: ["light", "dark", "system"] }),
+    limits:       flag({ type: "json", default: { daily: 10, burst: 50 } }),
   },
 });
 ```
 
-Author it: `palbase flags add new_checkout --type boolean --default false`. On
+Four types: `boolean`, `number`, `string`, `json`. A `json` flag's default is an
+object (not an array, not a scalar) and nests at most 3 deep. `variants` is for
+`string` only — the flags service rejects it on every other type.
+
+Author it: `palbase flags add new_checkout --type boolean --default false`, or
+`palbase flags add limits --type json --default '{"daily":10}'`. On
 deploy, the definitions are upserted to the flags service (idempotent). A flag
 removed from the file is **not auto-deleted** (orphan definitions are harmless).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@palbase/backend",
-  "version": "10.0.0",
+  "version": "10.2.0",
   "description": "Palbase Backend SDK — class controllers (@Controller/@Get/@Post + @Body/@QueryParams/@Param), error classes, schema DSL",
   "license": "MIT",
   "repository": {