| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Kittybox can now ship with several different stylesheets, provided by
the renderer. Unknown stylesheets fall back to the default one, which is
the same Kittybox has shipped since its inception.
There's also a settings field for custom CSS, but it's not exposed
anywhere yet.
Change-Id: I2850dace5c40f9fed04b4651c551a861df5b83d3
|
|
|
|
| |
Change-Id: I80e81ebba3f0cdf8c094451c9fe3ee4126b8c888
|
|
|
|
|
|
|
|
| |
This is a little bit more idiomatic.
Perhaps I should consider doing the same with other tuples I return?
Change-Id: I85f0e5dc76b8212ab6d192376d8c38ce2048ae85
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some breaking changes. For better or for worse. The optional extractor
breaking change is a double-edged sword, since not all extractors can
be used with `Option<T>` now, and you have to use
`Result<T, T::Rejection>` even when you want to ignore an error coming
from an extractor, such as `Query`.
However, this allows catching errors on authorization extractors even
in places where authorization is optional.
Change-Id: I35f809d3adf27dbef0e7ee93dc1a7af178b7d014
|
|
|
|
|
|
|
| |
It just does its thing in the background, potentially speeding up
things. Maybe I could also use the underlying in-memory cache
implementation (Moka) to speed up my database. I heard crates.io got
some good results from that.
|
|
|
|
|
|
| |
The warnings only remain in places where I need them to remain,
because I either need a reminder to implement something, or I need to
refactor and simplify the code in question.
|
|
|
|
|
| |
This somehow allowed me to shrink the construction phase of Kittybox
by a huge amount of code.
|
|
|
|
| |
This makes the interface more consistent and resistant to misuse.
|
|
|