Feedback request: async YNAB API client (self-taught, ~1 year Rust)

code review
1

I am still relatively new to all this. I have no background in the industry and started learning Rust about a year ago. I built an async client for the YNAB (You Need a Budget) API. It's my most substantial Rust project. I'm looking for honest feedback to help me grow as an amateur developer.

Specific Questions I have:

  1. Does the builder pattern feel ergonomic for a library user?
  2. I tried consolidating my http methods, but ran into some implementation issues. Anyone have good ideas to de-duplicate this code?
  3. I originally wrote this library in Go and carried over tuple returns for endpoints that return a server_knowledge i64. Would I be better off creating a wrapper struct?
  4. I added an optional polars feature to enable data analysis. Is this a smart choice or should I pull that out into a separate crate? I know I should add some tests to this feature, but I'm not sure if it even belongs yet.
  5. What do you think of my unit test coverage and how I did integration tests?

Thanks for the consideration. I will pre-emptively toughen my skin for reactions.

2

I apologize as I don't yet have the experience to provide any meaningful code review, but I just wanted to say this looks great and might be genuinely useful to me. Nice work.

3

Well thank you kindly! If you wind up using it and run into issues, please let me know or open an issue. I'd really like this to be a useful library for people.