cargo-specification
cargo-specification copied to clipboard
The code is the spec
I should be able to specify path like that: ```toml thing = "@/some/path/to/file.rs" ``` instead of ```toml thing = "../../../../some/path/to/file.rs" ```
right now we can't configure the placeholder syntax `{ thing }` which collides with latex. It'd be good to change it to something like that `` perhaps (that wouldn't be...
rebrand
from str4d: > Binaries named cargo-foo do not look language-agnostic, as that naming specifically is for integration with cargo as cargo foo we should probably rename cargo-spec to something else,...
The code might be much easier if we just extract all the comments with something like https://docs.rs/comment-parser/latest/comment_parser/ so we can support many languages One problem is with instructions like `spec:startcode`,...
these lines: ```rust panic!("could not find file to watch {}", file.display()) ``` should probably be turned into just printing an error, as file watching should be fixed at the next...
here it is: https://github.com/martinthomson/i-d-template
Make sure that we can click on the code to jump to (Github) source
add latex to the respec stuff
First, I think we should have some good defaults when parsing files based on the file extension. Perhaps we can use this: https://docs.rs/comment-parser/latest/comment_parser/ Second, I think you should still be...
Github can detect machine generated file, and display them differently. For HTML it's here: https://github.com/github/linguist/blob/master/lib/linguist/generated.rb#L708 no implementation exists for markdown though in both cases it sounds like adding something like...