Elf M. Sternberg
8ee71c76a3
In the great tradition of TPP, this is a win. We've gone through the test driven development, and there is so much *learning* here: - tokio::test NEEDS the threaded_schedular feature to report errors correctly - thiserror can't do enum variants the way I expected - Different error types for different returns is not kosher - Serde's configuration NEEDS a type, such as JSON, to work, - Rust has include_str!(), to embed text in a Rust program from an external source - SQLX is still a pain, but it's managable. |
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| Cargo.toml | ||
| README.org | ||
README.org
- Notesmachine Store
- Plans
- Make it possible to save a note
- Make it possible to retrieve a note
- Read how others use SQLX to initialize the database
- Implement CLI features
- Make it possible to connect two notes
- Make it possible to save a page
- Make it possible to connect a note to a page
- Make it possible to retrieve a collection of notes
- Make it possible to retrieve a page
- Plans
Notesmachine Store
This is the storage layer for Notesmachine. It supports the retrieval of the basic information from Notesmachine, but it never reveals the underlying mechanisms by which it performs its magic. The "ids" leaving this API will always be the textual ids used in all public representations:
- Boxes are referenced by slugs, and clients must accept uniqueness failures.
- Notes are referenced by "friendly_id" format strings, which are base-62 formatted versions of UUID4 strings.