ticket

Roadmap

Ticket is built one milestone at a time. Tickets for a milestone are written when the one before it lands, so plans further out are scope, not promises.

F0: Skeleton (done)

The package builds, and an example app depends on it and serves a page.

F1: Request to response (done)

  • Done: Conn, params, URL and cookie parsing
  • Done: the views zone and Ticket.Html
  • Done: the view_component zone
  • Done: the routes zone with resources and path helpers
  • Done: controllers, responses, filters and the routes task
  • Done: the ticket CLI with new, server and routes

F2: Data (done)

  • Done: a Db effect backed by node:sqlite, with no npm install
  • Done: a migrations zone that generates records and insert types
  • Done: ticket db:*, ticket g migration and ticket g model
  • Done: model queries. A generated Posts effect and typed columns, so a misspelled column or a wrong value type is a compile error. See Database
  • Done: forms and validations. Params.record decodes a form into the insert type, and a validations zone adds presence, length, inclusion, format and uniqueness
  • Done: associations. references columns give belongs_to and has_many functions, and on_delete
  • Done: the blog example, examples/blog

F2 is done when a blog example creates, edits, lists and deletes posts in SQLite through generated models, and invalid input re-renders with errors.

F3: App ergonomics (done)

  • Done: form helpers as JSX components, <Forms.TextField />, <Links.ButtonTo />
  • Done: signed-cookie sessions, flash and CSRF
  • Done: static files, request logging and a development error page
  • Done: generators: g controller, g scaffold, destroy
  • Done: test helpers and ticket test
  • Done: ticket console, which needs a polar repl that imports modules in folders (polar-lang P14)

F3 is done when ticket generate scaffold produces a working CRUD resource, and the blog's e2e covers flash and a CSRF rejection.

F4: Ready to ship (done, 0.2.0)

  • Done: ticket server --watch rebuilds and restarts on edit
  • Done: authentication. Ticket.Auth hashes passwords, login rotates the session and require_login is a filter. ticket g auth writes the users model, the controllers and the views
  • Done: query depth. in_list, gte, lte, Query.any, aggregates, paginate and eager loading
  • Done: JSON requests and responses, multipart uploads and body limits
  • Done: production hardening. Graceful shutdown, GET /up, default security headers, JSON request logs and a Dockerfile from ticket new
  • Done: install.sh for the ticket command

F4 is done when a fresh ticket new app, with login, runs in a container and stops cleanly on SIGTERM.

What's next

  • A Postgres adapter
  • A native ticket CLI that doesn't need a checkout
  • Test-runner depth: per-file setup, expected errors, and a workspace of test files
  • Background jobs and mailers
  • Websockets
  • An asset pipeline
  • i18n
  • Multiple databases at once