docs: add quickstart - #52
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #52 +/- ##
=======================================
Coverage 99.06% 99.06%
=======================================
Files 6 6
Lines 532 532
=======================================
Hits 527 527
Misses 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
ba9005f to
efa1d33
Compare
|
this is great, but can you add some example output for the code snippets? (output of the print statements, for example) |
Co-authored-by: Alyssa Travitz <31974495+atravitz@users.noreply.github.com>
@atravitz I like this idea. Should we create the example as a "complete" Python file so that we can run this independently? We can even link to it at the end as a complete example. |
yeah go for it! |
2430c75 to
f4ffb0e
Compare
|
looks great, but when I run locally I get the following error: |
This generally occurs because you run the script twice consecutively. This makes sense because task-ids are unique to inserting a duplicate ID should fail. I debated whether or not we should name task databases in the example with UUIDs because it enables us to just keep running the script over and over. The other alternative is to use an in-memory database instead of one on disk. |
The code-block:: sh directives had too many arguments on the same line, causing RST parsing errors. Fixed by using proper RST syntax with the language/class specified on the directive line and the content indented on following lines. Assisted-by: Pi:opencode/nemotron-3.5-lightning-free
b847b3d to
63ebac4
Compare
ah, very possible. Is it possible to have nicer error handling for this in general? But yeah UUIDs might be good. non-blocking though, I think this is a significant improvement! |
|
Going to add a nicer error and then merge. |
This PR will followup from the work in #47 to move our "micro-dashboard" to a more usable walkthrough.