I’m developing a library that does some heavylifting when you’re building REST API’s.
It includes some important pieces for API dev and functions as a headstart in the process, at the cost of some configuration. And it has some neat features at the cost of some assumptions regarding the role of the API.
It is in continous development and I’m looking for some feedback before I get it running on nuget.
I would love to get some opinions and criticism on this as I’m the sole adventurer of this project.
Unfortunately it dosen’t exist alot of documentation yet, although there is a brief introduction at the repo.
Best wishes!
https://github.com/gnilsson/Rapier/
I think the project will suffer the same problems others like it have. Most software doesn’t fit into a REST model. You end up with RPC endpoints and you’re better off making a backed that matches exactly what you need instead of a generic REST endpoint. If it solves your problems please continue working on it. Everyone should have side projects.
Yes you have a good suspicion, applying this correctly will be equally as difficult as creating it if you have a big project in mind. I will definitely do that, thanks
Many questions come up:
how do I configure filters on per action/controller basis?
how do I add parameters to actions?
do I need code generation for clients?
Thoughs:
for blazor usage it would be nice to have single interface in shared assembly. Backend implements it with your library, and blazor client ‘just somehow’ get the client implemented. You know kinda what . Net-Remoting used to be
you might want to use some query-like syntax for your responses instead of limiting pageIndex/pageSize – oData/graph-ql
Authorize filter is customizable per action from configuration, were there any other specific filters you had in mind? Might be worth to extend that configuration in that case.
Parameters are added in a entity request model and is usable from Get, Create & Update endpoints. To add query parameters you need to create a class that inherits a parameter baseclass e.g StringParameter and reference the property.
My initial thought was to create a tailored client but nswag code gen I realized is pretty great. I might still opt for the first choice down the line though, for sure possible.
Hmm I’m not sure I follow, to change the query syntax, and what do you mean with limiting?
C# devs
null reference exceptions