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
viewszone andTicket.Html - Done: the
view_componentzone -
Done: the
routeszone with resources and path helpers -
Done: controllers, responses, filters and the
routestask -
Done: the
ticketCLI withnew,serverandroutes
F2: Data (done)
-
Done: a
Dbeffect backed bynode:sqlite, with no npm install -
Done: a
migrationszone that generates records and insert types -
Done:
ticket db:*,ticket g migrationandticket g model -
Done: model queries. A generated
Postseffect and typed columns, so a misspelled column or a wrong value type is a compile error. See Database -
Done: forms and validations.
Params.recorddecodes a form into the insert type, and avalidationszone addspresence,length,inclusion,formatanduniqueness -
Done: associations.
referencescolumns give belongs_to and has_many functions, andon_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 apolar replthat 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 --watchrebuilds and restarts on edit -
Done: authentication.
Ticket.Authhashes passwords,loginrotates the session andrequire_loginis a filter.ticket g authwrites the users model, the controllers and the views -
Done: query depth.
in_list,gte,lte,Query.any, aggregates,paginateand 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 aDockerfilefromticket new -
Done:
install.shfor theticketcommand
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
ticketCLI 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