Releases: thomasp85/fiery
Releases · thomasp85/fiery
fiery 1.2.1
fiery 1.2.0
- Update to work with new future release
- Move from assertthat to rlang based type checking
fiery 1.1.4
- General upkeep (new CI, redocument, etc)
fiery 1.1.3
- Avoid tests that fails on some CRAN machines due to new testthat version
fiery 1.1.2
- Fix bug where delayed logging would result in wrong message being logged (#39)
- Remove some tests as new later architecture makes certain async operations
untestable (#40) - pkgdown site now available at https://fiery.data-imaginist.com
Fiery 1.1.0
- Add logging API. Set custom loggers with
set_logger()
and send messages to
the log withlog()
. Logging is automatically delayed so it doesn't slow down
request and message handling (#18). - Added
access_log_format
field to define how requests are logged. - Added
is_running()
method to query the state of the server. - Capture errors in each handler for events and delayed execution, so that
evaluation of the other handlers are unaffected (#20). - Document the use of delayed evaluation. See
?delay_doc
Fiery 1.0.0
This is the first major release of the Fiery web server framework. It includes a number of breaking changes to the prior version released on CRAN in order to clean up the API and set it up for a stable life afterwards.
Fire$new()
now takes a port and host argument to set these fields on
initialisation. (fixes #5)- BREAKING Results from before-request and before-message events are now
passed on to the request and message handlers as a list in thearg_list
argument rather than as single arguments. - The host and port are now advertised when a server is started/resumed (#11)
- Fire objects now has a print method (#12)
- BREAKING fiery now uses the
reqres
Request and Response classes for
handling http exchange. - BREAKING
attach()
now expect aon_attach()
method rather than a
onAttach()
method from the plugin. It also expects aname
field and
optionally arequire
field - BREAKING The
header
event now expect handlers to return a logical, with
TRUE
indicating further processing, andFALSE
indicating termination. - Cycle events are now triggered when running with
block = FALSE
making the
two run modes identical in their life cycle events. - BREAKING The
after-request
event will no longer pass the response to
handlers. This can be retrieved from therequest
object. - The server can now be mounted at a path, which will strip that path from
request paths thus making the app logic independent on mounting. Use the
root
field to access and change the root location. - Websocket connections can now be closed from the server by using the
close_ws_con()
method. - Better documentation. Events and plugins now has their own documentation
entries (fixes #10). - Convert roxygen documentation to md format
- BREAKING fields now uses snake_case rather than camelCase for a more
consistent interface. This meansrefreshRate
->refresh_rate
,
triggerDir
->trigger_dir
. - Switch to MIT License
- Catch errors in start and resume event handlers