Building apps with Rwf guide, request session not optional, better ORM interface, other fixes #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Breaking changes
Request::session()
now returns theSession
instead ofOption<Session>
. This reinforces the guarantee that all Rwf requests will have a user session, even if the browser doesn't respect cookie settings.Features
hash
andhash_validate
using Argon2.argon2
crate added as dependency torwf
.Other changes
Option<T: Model>
forToTemplateValue
, allowing to pass in optional results from ORM directly into the template.render!
macro when specifying response code.