Sergio Benitez
a15002877d
Use connection pool in todo example.
2017-02-02 18:01:00 -08:00
Sergio Benitez
1a18c73970
Update to todo example to diesel 0.10.
2017-02-02 14:47:53 -08:00
Sergio Benitez
5fabb43a1b
Update to serde 0.9, handlebars 0.25. Move from `map!` to `json!` macro.
...
Resolves #154 .
2017-01-31 17:15:42 -08:00
Sergio Benitez
c1697509ba
Improve lints: gather info on per-instance basis.
2017-01-31 02:01:30 -08:00
Sergio Benitez
44e367c64c
Remove authorship from all examples.
2017-01-19 17:14:01 -08:00
Sergio Benitez
3d0f7f2f80
Clarify todo example requirements.
2016-12-27 02:38:21 -06:00
Sergio Benitez
0be423a35e
Updated dependency versions.
2016-12-09 20:14:49 -08:00
Sergio Benitez
a9b12568d9
Update to upstream diesel.
2016-10-12 00:38:30 -07:00
Sergio Benitez
6275e576b5
Updates for latest nightly. Use Tera from main branch.
2016-10-08 19:27:33 -07:00
Sergio Benitez
920bd35d46
Update serde in examples.
2016-10-03 17:56:43 -07:00
Sergio Benitez
f74e286e31
Add templating support in contrib crate.
...
The contrib crate now contains support for both Handlebars and Tera. No
documentation yet.
resolves #5
2016-09-22 04:12:07 -07:00
Sergio Benitez
46f73ed57c
Renamed macros to codegen.
2016-09-08 20:38:58 -07:00
Sergio Benitez
1f19b88803
Use forked diesel to compile on latest nightly.
2016-09-04 14:24:48 -07:00
Sergio Benitez
025c9243c0
Now using a Cargo workspace for (much!) faster builds. Added a temporary query
...
params example.
2016-08-10 17:50:08 -07:00
Sergio Benitez
d16d9bd0d7
Fixed todo example. Testing script now bootstraps when needed.
2016-08-06 19:57:44 -07:00
Sergio Benitez
b767c1bdec
Fixed Cargo.toml in todo for new diesel. Serde is still broken.
2016-08-05 21:57:55 -07:00
Sergio Benitez
578b50b1f9
Fully working todo example. Apparently didn't commit in a while. Need to be better at that.
2016-08-01 19:07:36 -07:00
Sergio Benitez
26b7b814f4
Progress on errors. Started Todo example.
...
The error function now takes in a "RoutingError" structure. The idea is that the
structure includes all of the information necessary for a user to processor the
error as they wish. This interface is very incomplete and may change. At a
minimum, the error structure should include:
1) The request that failed.
2) Why the request failed.
3) The chain of attempted route matches, if any.
4) Something else?
2016-07-15 21:09:08 -07:00