Feedback request: async YNAB API client (self-taught, ~1 year Rust)
⚓ Rust 📅 2026-05-19 👤 surdeus 👁️ 1I 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:
- Does the builder pattern feel ergonomic for a library user?
- I tried consolidating my http methods, but ran into some implementation issues. Anyone have good ideas to de-duplicate this code?
- I originally wrote this library in Go and carried over tuple returns for endpoints that return a
server_knowledgei64. Would I be better off creating a wrapper struct? - I added an optional
polarsfeature 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. - 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.
1 post - 1 participant
🏷️ Rust_feed