12 releases

0.6.2 Sep 27, 2023
0.6.0 Jan 14, 2023
0.5.1 Jul 27, 2022
0.4.2 Nov 7, 2021
0.1.0 Jul 30, 2019

#42 in HTTP server

Download history 4303/week @ 2023-11-02 2534/week @ 2023-11-09 2428/week @ 2023-11-16 2221/week @ 2023-11-23 2290/week @ 2023-11-30 2278/week @ 2023-12-07 2146/week @ 2023-12-14 1295/week @ 2023-12-21 1154/week @ 2023-12-28 1840/week @ 2024-01-04 2977/week @ 2024-01-11 2969/week @ 2024-01-18 3740/week @ 2024-01-25 2118/week @ 2024-02-01 2635/week @ 2024-02-08 1996/week @ 2024-02-15

11,097 downloads per month
Used in 11 crates (via paperclip)

MIT/Apache

6MB
35K SLoC

JavaScript 21K SLoC // 0.1% comments JSX 11K SLoC // 0.0% comments Rust 3K SLoC // 0.0% comments Shell 90 SLoC // 0.2% comments Bitbake 41 SLoC // 0.1% comments

Paperclip

Build Status Linter Status Usage docs API docs Crates.io

Paperclip offers tooling for the OpenAPI specification. Once complete, it will provide:

  • Code generation for efficient, type-safe, compile-time checked HTTP APIs (server, client and CLI) in Rust.
  • Support for processing, validating and hosting OpenAPI spec.
  • Customization for spec and code generation.

It's currently under active development and may not be ready for production use just yet.

You may be interested in:

Developing locally

  • Make sure you have rustup installed. cd into this repository and run make prepare to setup your environment.
  • Now run make to build and run the tests.

Contributing

This project welcomes all kinds of contributions. No contribution is too small!

If you want to contribute to this project but don't know how to begin or if you need help with something related to this project, feel free to send me an email (in Github profile) or join the Discord server.

Code of Conduct

This project follows the Rust Code of Conduct.

License

Licensed under either of

at your option.

Sponsors

Folks who have sponsored for the development of this project:

FAQ

Why is this generating raw Rust code instead of leveraging procedural macros for compile-time codegen?

I don't think proc macros are the right way to go for REST APIs. We need to be able to see the generated code somehow to identify names, fields, supported methods, etc. With proc macros, you sorta have to guess.

This doesn't mean you can't generate APIs in compile-time. The only difference is that you'll be using build scripts instead and include! the relevant code. That said, we're using proc-macros for other things.

The error thrown at compile-time doesn't look like it's very useful. Isn't there a better way to do this?

None that I can think of, sadly.

New ideas are here needed.

Dependencies

~3–17MB
~229K SLoC