Release 0.8.2

The Jetty dependency is now a runtime dependency, not a compile-time dependency (for when you want to use http-kit -- although Ring itself brings in the Jetty adapter, but that's outside the framework.one namespace).

Release 0.8.1

• Add (abort rc) to short-circuit the controller lifecycle.
• Ensure after / :after runs even when rendering or redirecting.

Release 0.8.0

Potentially breaking release. Some APIs have changes a little, as has the way that core request metadata is held inside the rc.

The rc now contains the entire original Ring request (as :framework.one/ring) and the FW/1 per-event metadata (as :framework.one/event). The previous :framework.one/request structure has been removed. Several of the APIs that previously operated on that now operate directly on the Ring request structure. This has streamlined a number of operations within the framework, as well as making it easier to add Ring-related enhancements, and handle custom Ring middleware.

Other changes:

• You can no longer read the 'flash' scope, only update it.
• (parameters rc) returns the request context without the Ring and FW/1 metadata (for when you want to iterate over the elements of the request context, such as form scope data).
• (ring rc) has replaced (ring rc name) so that you can easily access the whole Ring request.
• (scope-access scope) has been removed. It was mostly an internal convenience and was never really intended for public use.
• A first draft of clojure.spec specifications now exists for the request context (and the FW/1 event and Ring metadata), in framework.one.spec. This will evolve over the next few releases, based on real world usage. Feedback welcome!

Release 0.7.5

• Add ring scope to access original Ring request elements -- #46
• Expand servlet-request to proxy additional methods -- #46

Release 0.7.4

• Add optional status to redirect -- #45
• Add render-raw-json -- #44

Release 0.7.3

Standardize middleware (uses Ring's site-defaults with XSRF Anti-Forgery disabled -- you can easily opt-in if you want).

Also cleans up the rendering, routing, and handling code.

Release 0.7.2

Standardize web server startup; standardization wait for server shutdown; coerce id route parameter to int.

Release 0.7.1

• Adds default-handler with basic Compojure routing.
• Configured router now supports (fw1 :section) as shorthand for default item in that section.

Release 0.7.0

*** BREAKING CHANGES ***

This release switches all the routing to use Compojure. Implicit routing is no longer provided. The entry point for the framework has changed to configure-router. See the README and the examples/usermanager/main.clj file for guidance on the new way to use the framework.

FW/1 now assumes you'll be using Stuart Sierra's Component library as well as Compojure for routing.

Release 0.6.0

The version bump is due to switching JSON generation from clojure.data.json to Cheshire which may change some data formatting.

• #37 - Switch JSON generation to Cheshire
• #36 - Missing view now returns 404 Not Found instead of 500 missing resource exception
• #35 - Route mappings can now have an HTTP status code (301, 302, 403, 404, 405)
• #34 - A route pattern of /* is now allowed
• #33 - render-html has been added
• #32 - The render-xxx functions all accept rc, data or rc, status, data now to allow HTTP status values to be set
• #29 - Partial support for OPTIONS requests has been added