cargo-readme VS server

There’s also this cargo-readme

cargo readme does this (specifically for crate-level documentation), not sure if that’s helpful for your usecase :)

Link in case it's not just me that want aware of it.

The README.md isn't part of the rust code, so it's not checked by this unless you use tools to generate your README from doc comments like https://github.com/livioribeiro/cargo-readme.

I find myself repeating myself between crate-level doc comments and README files. What are people using to avoid that? cargo-readme + a CI hook?

I created Server.js https://serverjs.io/ and still use it. It is a wrapper around express:

- With a bunch of middleware included and pre-configured, like body-parser, cookies, Helmet, etc. All express middleware works with Server.js

- async/await routers as expected: get('/users', async (ctx) => {...}); (ctx inspired by Koa)

- Websockets, where messages behave just as another route: socket('message', async ctx => { ... });

I did that! I hope you are not the person who suffered that from me (did you use Picnic CSS a few years back?). So for a newer project I put some setup code that will look for all code snippets with a specific comment and run that with the code after the comment. For generating the website documentation that test bit can be stripped (though I kept it for now).

Example: https://github.com/franciscop/server/blob/master/docs/docume...