Hi!
As discussed on mastodon, I thought it would be a good idea to provide a translation layer (wrapper) for backends of the v3 client.
This was an issue in the past, during the v2->v3 migration: you had to have two backends in order to smoothly transition from full-v2 to full-v3 usage.
I propose, if possible, to provide a module that allows wrapping any v3 backend (maybe with a limitation of no streaming, if that helps) and get a v4 backend back. That way, there will only be one underlying backend implementation to carry around, and wrapping can happen at the use site instead of when bootstrapping the application.
Note: This is a bystander suggestion, I'm not actively using sttp these days, and probably won't be affected by the migration. This may impact my judgement on how useful/easy to implement this is ;)
Hi!
As discussed on mastodon, I thought it would be a good idea to provide a translation layer (wrapper) for backends of the v3 client.
This was an issue in the past, during the v2->v3 migration: you had to have two backends in order to smoothly transition from full-v2 to full-v3 usage.
I propose, if possible, to provide a module that allows wrapping any v3 backend (maybe with a limitation of no streaming, if that helps) and get a v4 backend back. That way, there will only be one underlying backend implementation to carry around, and wrapping can happen at the use site instead of when bootstrapping the application.
Note: This is a bystander suggestion, I'm not actively using sttp these days, and probably won't be affected by the migration. This may impact my judgement on how useful/easy to implement this is ;)