Files
PiCloud/examples/cms-poc/scripts/comments/comments_for_post.rhai
MechaCat02 813bc46640
Some checks failed
CI / Rust — fmt, clippy, test (push) Failing after 39m53s
CI / Dashboard — check (push) Successful in 10m15s
docs(examples): add the CMS proof-of-concept dogfooding artifact
A WordPress-inspired CMS whose entire backend is PiCloud Rhai scripts
deployed with pic apply, plus a SvelteKit frontend. Built to dogfood the
project tool, CLI, and SDK; exercises docs/kv/files/users, docs+queue+cron
+pubsub triggers, the transactional-outbox notification chain, a docs
before-interceptor, set_if CAS, SSE, per-app CORS, env overlays, and a
durable Workflow (validate -> enrich || seo -> publish -> finalize) started
with workflow::start and polled with workflow::run_status, visualized live
with Svelte Flow.

FINDINGS.md / SECURITY.md capture every gap, surprise, and security issue
found (each tagged [PiCloud] vs [CMS]); the platform fixes for the
actionable ones ship in the preceding commit.

Also folds in the read-only `pic` allowlist entries added to
.claude/settings.json during the session (fewer-permission-prompts).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-19 20:15:29 +02:00

18 lines
517 B
Plaintext

// GET /cms/posts/:id/comments — public list of APPROVED comments for a post.
import "util" as util;
let post_id = ctx.request.params.id;
let comments = docs::collection("comments");
let rows = comments.find(#{
post_id: post_id,
status: "approved",
"$sort": #{ created_at: 1 },
"$limit": 200,
});
let out = [];
for r in rows {
let c = util::shape_doc(r);
c.remove("author_email"); // never expose commenter emails publicly
out.push(c);
}
#{ statusCode: 200, body: #{ comments: out } }