Skip to content

Add one NestJS, Fastify, or Python boundary example — no assignment needed #47

Description

@aoto-tech

Start from an existing example

Choose one starting point; one small improvement is enough. You do not need to design a complete application.

Starting point A concrete contribution
Fastify route fixture Turn this static route-contract example into a short documented example under examples/fastify-routes/
NestJS route fixture Add a documented controller/resource-contract example under examples/nestjs-routes/
Python service example Expand its README with the actual cell/file layout and one reproducible private-import violation

For a new example, reuse the demonstrated source and manifest shape, adjust paths as needed, and explain what the contract enforces. Keep the default state valid. Demonstrate a violation separately through a reversible edit or temporary copy.

For a README improvement, editing that README alone is acceptable when it fully addresses the gap. More examples and distinct improvements to existing ones remain welcome; no framework is reserved.

What to include

  • The boundary or resource contract being demonstrated.
  • Copyable commands, required versions, and actual expected results.
  • Relevant analysis limitations.

A static fixture does not by itself establish a runnable framework application. State what the example demonstrates; verify framework execution if you claim it runs. Keep dependencies minimal and the CellFence demonstration independent of live services.

Validation

npm ci
npm run build
node --test tests/examples.test.mjs
git diff --check

Also run the example's documented commands. Follow CONTRIBUTING.md · AGENTS.md; report what ran and what did not. Default examples must pass; deliberate violations must produce the documented rule IDs. Do not weaken the checker to make an example pass.

Multiple contributors welcome, including AI agents and bots. No assignment, reservation, or advance comment is needed. Check existing files and open PRs, fork the repository, and submit one useful improvement per PR. Different improvements to the same subject remain welcome. No deadline or contributor limit. Use Refs #47; this issue stays open after individual PRs merge.

Related: #20 covers a generic two-cell demo. Check existing PRs before implementing the same change.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomershelp wantedExtra attention is neededtestingTest coverage, fixtures, and validation work

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions