Elf M. Sternberg
1b8e1c067d
This is mostly an exercise to understand the derive_builder pattern. It required a few tips to get it working, but in the end, it's actually what I want. I also learned a lot about how the Executor pattern, the Results<> object, error mapping, and futures interact in this code. This is going to be incredibly useful long-term, as long as I still keep this project "live" in my head. |
||
|---|---|---|
| .. | ||
| docs | ||
| src | ||
| .gitignore | ||
| Cargo.toml | ||
| Makefile | ||
| 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.