Further fixes to copy() and extend(). Circular references are no longer supported, however.
Removed a lot of unnecessary and complex copy() and extend() calls for a noticeable performance boost. There's less protection now against bad behavior (modifying param.session directly within controllers, for example), so if you access the params argument directly...test thoroughly :)

0.8.0

published 0.8.0 • 7 years ago

Changelog

BREAKING CHANGES (see readme for details):
- Updated dependencies to latest versions
- The built-in Jade and Handlebars template engines have been replaced with consolidate.js (https://github.com/tj/consolidate.js). Simply install your preferred engine, add it to your dependencies, and set the "templateEngine" config setting. Handlebars is included by default.
- Config change: the server "hostname" setting has been changed to "host" so as to avoid confusion with the HTTP/HTTPS server hostname settings
- The copy() and extend() helpers have been updated for improved accuracy within the framework, which means some bad behavior that was tolerated previously will no longer work. Please test any code that relies on these methods to ensure it still behaves as expected.
- CORS support has been enhanced to provide unique attributes to each controller action, so the notation in the controller has changed
- Cache-Control settings for cached routes should now be handled using the new HTTP Header directive rather than route.cache.control
Deprecations
- All helpers except for cache() and log() have been deprecated and will be removed from the public app scope in 0.9.0. Any of the deprecated helpers can be replaced by native functionality (Promises in place of listen() for example) or a third-party library. cache() and log() are still pretty nice though (imho), so I'm keeping them public.

0.7.19

published 0.7.19 • 7 years ago

Changelog

Deprecations (these items will no longer be supported by citizen as of v0.8.0):
- The "access" module export that enables CORS support at the controller level will be replaced with a "headers" directive that works at the controller action level.
- The developers of Jade have renamed the project to Pug with all new updates being performed under the Pug name. citizen will drop support for Jade and replace it with the new Pug engine. There are a few breaking changes in Pug: https://github.com/pugjs/pug/issues/2305
Fixed an issue where "Accept-Encoding: gzip;q=0" would still provide gzip encoding because it was the only encoding specified (encoding now defaults to identity)
Official minimum node version has been bumped to 6.11.x

published 0.7.18 • 8 years ago

Changelog

published 0.7.17 • 8 years ago

Changelog

published 0.7.16 • 8 years ago

Changelog

The accepting-encoding parser has been rewritten to be conformant
The compression engine has been rewritten to support deflate
A potentially breaking change: The default configuration has been changed to disable JSON and JSONP global output by default, which is safer. You can enable each one individually in the global config, causing all controllers to allow output in those formats, or enable JSON or JSONP output at the controller level using the new "formats" parameter.
HTML output can now be disabled completely at the global config level or controller level
Pretty output for HTML and JSON is now driven by the framework mode rather than config values. In debug and development modes, output is pretty. In production mode, output is ugly (minified).