View gradio api and macro

[denizsincar29]

I have a great idea and a question:
How to quickly prety print or save to txt the gradio space api? Manually iterate over endpoints and arguments?
Idea:
What if we make a macro that generates code and functions to use with some api? e.g.
let Client = client::new_sync(params);
let endpoint = client.generate_endpoint!();
endpoint.transcribe(text, param1, param2);

[JacobLinCool]

Both AppConfig and ApiInfo (which can be obtained using .view_config() and .view_api()) can be serialized by serde. But this is far from "pretty" printing, and I don't know if that's what you want.

I think your macro is good for DX and type checking. I haven't looked into Rust macros before, but I thought if there were some similar examples like converting openapi to client, I might be able to figure this out. Do you have experience doing this?

[denizsincar29]

@JacobLinCool I will try making a simple macro for this and show you, but is it possible to move to private messaging for example in telegram?

[denizsincar29]

@JacobLinCool Hello! I've recently wrote you on discord and telegram, I've updated gradio macro crate and i was thinking to move from anyhow to thiserror for better error handling, but does your gradio rs use anyhow for internal error handling? Also, i constantly get a warning that a space works on gradio 6 but this client works on gradio 4 and 5, but gradio 6 is supported in your gradio_rs.

[JacobLinCool]

Hey @denizsincar29! I just merged #9 which addresses both of your points:

• Migrates the core library from anyhow to a typed error model using thiserror.
  There’s now a gradio::Error enum with specific variants (e.g. LoginFailed, StreamEndedUnexpectedly, RemoteError, etc.) and a gradio::Result<T> alias.

  That said, anyhow is still re-exported (pub use anyhow) temporarily so that downstream crates don't break during the transition. Feel free to move gradio_macro to thiserror.

• The version check now accepts major versions 4, 5, and 6, so the warning should go away.

Would love to hear if you run into any issues with the new error types on the gradio_macro side!