Make this toolkit/adapter more versatile and available for ASP.NET/web tools.
@Tom-Kingstone ci sta già lavorando.
Dal 8/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Description:
From my own experience developing web applications, it would be great if I didn't have to write a custom API client with its own BHoM serialiser/deserialiser every time I need to send BHoM objects to and from an API. For this purpose, the HTTP_Toolkit has potential to be useful, but it just isn't developed enough and doesn't allow enough direct customisation to be useful in many cases.
At least having both POST and GET (as push and pull) fully implemented would be a great start, and DELETE should be simple enough. It would also be necessary to have a constructor for the adapter that accepts an HTTP client that the adapter would use to make requests (as opposed to the current where new HTTP clients are created with each request) as some frameworks use HTTP client factories that set up clients in a specific way which isn't possible to use with this toolkit as it is.
Suggest possibly having custom config to allow choosing what form the response comes in (for instance I have in the past written POST endpoints which return a usable BHoM object response so at least that would need to be implemented as an option, or even as default if json response is detected).
- Lingua principale
- C#
- Stelle
- 2
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di BHoM/HTTP_Toolkit
-
type:compliance
BHoM/HTTP_Toolkit#123 · 1 assegnatario ·
-
type:bug
BHoM/HTTP_Toolkit#72 · 1 assegnatario ·
-
type:feature
BHoM/HTTP_Toolkit#52 · 1 commento · 2 assegnatari ·
-
HTTP GetRequest workflow Apertaseverity:low type:compliance type:question
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
BHoM/HTTP_Toolkit#20 · 5 commenti · 1 reazione ·
-
The number of responses resulting in the Pull is not of the expected length when using BatchRequest Apertatype:bug
BHoM/HTTP_Toolkit#13 · 2 commenti · 1 assegnatario ·
Tutte le issue di BHoM/HTTP_Toolkit
Issue simili
-
bug frontend good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
CS0162 "Unreachable code detected" warning from a MSBuildTemp .tmp file in every game project Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
-
Type: enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
apache/arrow-adbc#4809 ·