.
minor | *
Major | +
Addition | ^
improvement | !
Change
For the
0.1.x
releases, there may be some changes to types or API naming. Therefore, the version should be locked to the latest version used, for example,=0.1.0
. I will try to keep changes to a minimum, if any, and document them in the future CHANGELOG.Once
0.2.0
is released, I will adhere more strictly to the semantic versioning methodology.
+
addRouterBuilder::extend_resources(..)
!
renameRouterBuilder::set_resources_builder(..)
toRouterBuilder::set_resources(..)
^
AddIntoHandlerError
forString
,Value
, and&'static str
.^
Add HandlerError::new:().
removestd::error::Error
error requirement for HandlerError .error
Note:
v0.1.1
changes from0.1.0
router.call(resources, request)
was renamed torouter.call_with_resources(request, resources)
.- Now, the Router can have its own resources, enabling simpler and more efficient sharing of common resources across calls, while still allowing custom resources to be overlaid at the call level.
router.call(request)
uses just the default caller resources.See CHANGELOG for more information.
Rust10x rust-web-app has been updated.
!
Changedrouter.call(resources, request)
torouter.call_with_resources(request, resources)
.+
Router
can now have base/common resources that are "injected" into every call.- Use
router_builder.append_resource(resource)...
to add resources. - The method
router.call_with_resources(request, resources)
overlays the call resources on top of the router resources. router.call(request)
uses only the Router resources.
- Use
^
router_builder!
macro now allows building the route and resource.
let rpc_router = router_builder!(
handlers: [get_task, create_task], // will be turned into routes
resources: [ModelManager {}, AiManager {}] // common resources for all calls
)
.build();
*
Initial