Closed NullVoxPopuli closed 5 years ago
Regarding F#, I'm not sure. I've honestly never tried it, but there's no obvious reason (to me) why it shouldn't work. I'd be happy to work with you on it if you need any support. Although, it was not designed with a functional programming use case in mind, so it may be awkward. That is purely conjecture since I have no experience using this in an F# application.
Regarding just serialization, that's a very small part of this library and while it is part of our roadmap to make that possible, there is one blocker at the moment.
Sounds good, yeah, I'll give it a go. F# has objects and stuff, cause all of dotnet is compatible with all dotnet-languages. F# doesn't have all the OO features that C# does, but that's fine. (F# is OO in the same way python is / isn't)
I guess, re: just (de)serialization, I'm mostly wanting to have the functionality provided by http://jsonapi-rb.org which is:
I'm still pretty new to F#/dotnet web dev, and so far, it seems that this library has all the features I'd want (even if it has more, and I'd be using a subset).
speaking of which, are there any guides for using JsonApiDotNetCore with the entity framework? (or any other ORM?)
The reason why I don't really want to use a jsonapi only web framework is just in case I need an endpoint with non-jsonapi format.
As for web frameworks, I've been looking at https://github.com/SaturnFramework/Saturn, which is Giraffe-based -- so I was hoping to use jsonapidotnetcore with that :-)
anywho, I'll start playing with this in F#, and see what happens
Interested to know what you learned from this. Closing as no further action required.
just wondering, wanting to build a json:api api with fsharp, and this library seems the most feature-complete.
I guess, alternatively, is there a way to just use the (de)serialization parts? cause then I could just use whatever web server