![]() ![]() Until there's an official standard attribute then this functionality is always going to be held back. There are even third party implementations available, like this one that has 25k downloads (and the Binder one mentioned by somebody else above has nearly 250k):īut all of these workarounds usually involve some kind of additional attribute and struggle sometimes with more complex binding requests. So a further custom implementation is also required to produce the correct output for OpenApI. However, the lack of a first class implementation in ASPNET Core means that for example it is not so easy for Swashbuckle to natively implement this spec functionality either. This is also now a first class feature in the Open Api spec: A tighter integration with ASPNET Core would provide a more optimal, flexible and future proof implementation. There are workarounds as people have suggested, but these workarounds are unsupported and are often broken in new versions of ASPNET Core or with certain more complex binding scenarios and need re-adapting. Except this is not natively supported in ASPNET and IMO its become such a standard now that it should be. This is a common problem for which multipart requests are the accepted solution. ![]() ![]() This is required any time you need to send files to a RestAPI with additional structured data. OK, so sounds like this is the time window you need re-convincing on this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |