SOFA
SOFA copied to clipboard
Urigo
The best way to create REST APIs - Generate RESTful APIs from your GraphQL Server
Hello everyone and thanks a lot for your great work! I am already looking forward to integrate SOFA into our GraphQL-architecture. But before doing so, we must ensure that SOFA...
I haven't figure out how to resolve this issue yet. This libaray works fine when the schema is not too big. However, when I try to use a realworld schema...
Added method to split given url path into an array of path variables. Added cheks to ensure that path variables are not duplicated in the body.
Similar to [issue#1356](https://github.com/Urigo/SOFA/issues/1356) path parameters provided in the [RouteConfig](https://github.com/Urigo/SOFA/blob/master/src/sofa.ts#L26) interface are also displayed as parameters in the body of the request in Swagger docs. for example ``` { method: 'PATCH',...
I'm attempting to use Sofa in a Nestjs app, but the Rest endpoints are not receiving the data from post requests. Here's an example https://github.com/rafakwolf/nestjs-sofa-poc
I have a microservice API that is using SOFA and seems to be serving up data via REST just fine: ``` const { ApolloServer } = require('apollo-server-express'); const { buildFederatedSchema...
Is there any way of using it with fastify? I apologize if this question has already been asked, but I couldn't find anything in the repository
I've noticed an issue when generating mutation route schemas with the current version of SOFA. Specifically, I observed that the variables appear in both the request body and in the...
While GraphQL traditionally has a single entry point for all Queries and Mutations, REST usually organizes both across routes. For example, the following GraphQL Schema: ``` type Query { user(id:...
