Releases: atuttle/Taffy
Version 3.0.0 Release Candidate 3
Version 3.0.0 Release Candidate 2
There was a CF8 compatibility issue (#232) found in Release Candidate 1, which has been addressed. Thanks to @Damonmiller for the bug report and the fix!
Version 3.0.0 Release Candidate 1
A few bug fixes and additions have been made since the release of the 3.0.0-alpha. This build has been running stable for me for a few days now, so we're almost ready to call it stable. Please try this build and report any issues you have with it ASAP! We're not far from 3.0.0 final.
See the changelog here.
Version 2.2.6
Fixes a bug (related to #186) when you include query parameters with your request from the dashboard.
Version 2.2.5
Back-ported the fix for #186 into the 2.x branch.
Version 2.2.4
Added a new helper method named getExternalBeanFactory()
for use in your APIs. Previously, if you had created an external bean factory as a local variable in Application.cfc and set that into the framework as in:
var bf = createObject(...);
variables.beanFactory = bf;
... Then you would have no way to reference your external bean factory. This new method adds the canonical getter for that situation.
Thanks to @dskaggs for your time describing the use-case.
Version 3.0.0-alpha
See the full release notes in the documentation.
There are a few minor breaking changes that you should be aware of.
Version 2.2.3
Fixes an additional CF8 compatibility issue that wasn't found during the development of version 2.2.2.
Version 2.2.2
Bugs Fixed
- #153: Resurfaced: A CF8 compatibility issue. This has been resolved.
- #187: Changed logging default from email (to nobody, which could cause a lot of un-sendable email to pile up in your server's spool) to logging to the response buffer, which makes more sense for development. You'll want to change this in production, of course.
- Fixed a bug in time metrics reporting during the OPTIONS request phase of CORS requests.
- Fixed a bug where a resource with no methods defined would cause the dashboard to crash.
- #189: @jbvanzuylen fixed a bug where a successful response (status 204) with no response body (
return noData()
) would cause the dashboard to hang, waiting forever for the response. - #185: Posting a json array, rather than a structure, as the request body (see: #169) from the dashboard would cause error message "Looks like you're sending JSON data, but you haven't specified a content type. Aborting request."
New Features
- LogToScreen now always returns status 500
- #194: When pre-filling in the request body in the dashboard, body arguments now have the correct data type (strings, numerics, etc)
- #197: @sneiland added a
queryToStruct
helper for when you're expecting only a single row back, which does whatqueryToArray( qry )[0]
would do, but with a nicer syntax. - #193: Added buttons to the dashboard to hide the documentation and make the interactive request tools full-width.
Thanks
Special thanks to @sneiland and @jbvanzuylen this time for their contributions!
Version 2.2.1
Functionally identical to version 2.2.0; only now the version number has been updated in the dashboard to be correct. Sorry for the mismatch!