yes, no plans for other HTTP verbs just yet. However, if you have a use case for that, feel free to share.
I ended up setting this on the windows and mac machines: git config core.filemode false
seems like the issue of something fighting and changing the file mode back to cause permission denied has stopped. not really the answer probably but will suffice for me to get back up and running
i think the only use case is for API readability for external use. I think the use case of hilla was to tightly bind a frontend & backend, but I could see myself disabling csrf on the connect/* sections and then using it for other things. I saw that 2.0 is trying to expose something regarding openapi, so i wasn’t sure if there were plans at all
Ok, glad that it works now. Regarding the openapi.json, we treat it as an implementation detail at this point, and we use quite a few private extensions there. Thanks for the idea, it is indeed potentially useful with external tools and services.
i could also just move my logic in my endpoint methods up a layer and then implement normal spring restcontrollers for the API, not a super need right now. thanks for the info!