Nate Laff
Nate Laff
ApiOperationBase.ExecuteAsync() would be useful as well I think, assuming I'm following the correct patterns ;)
This is what I do... API Client [Multipart] [Post("/me/picture")] Task UploadPictureAsync([AliasAs("file")] StreamPart stream); API signature [HttpPost("picture")] public async Task PostPictureAsync(IFormFile file)
I use something like var file = Request.Form.Files[0]; await _client.UploadPictureAsync(new Refit.StreamPart(file.OpenReadStream(), file.FileName, file.ContentType));
No, you can see my definitions of the client and the API method above. I use IFormFile in the API, and StreamPart in the client. EDIT: Oh, I see what...
Do you want feedback on this, or do you pretty much have your plan in place already?
Yes, Finbuckle is great, and I use (and contribute to) it. I do not think there is any need to replicate features from that package, but to make it easier...
Yes the discovery endpoint I was considering as part of routing. In IS4 I currently implement my own IEndpointRouter to use the tenant. The cookie is easy enough to accomplish...
One thing I'm running into here is with blazor server, basepath strategy seems to have issues. On some calls I end up with '_blazor' as the attempted tenant name which...
yeah it seems to be modifying it on its own. i will try with the ignore identifiers, i missed that bit. honestly, after three days about to ditch blazor efforts....