Oglethorpe

3 anos depois e nada ainda

@GuilhermeLimaSP Vai por mim, o pessoal do pagseguro não da a mínima para a parte técnica do negócio, a melhor coisa que fizemos aqui foi migrar para o pagar-me, as...

I'm facing the same problem right know

Shure, thanks for asking: Here is my startup configuration: ```C# public class Startup { public Startup(IConfiguration configuration) { Configuration = configuration; } public IConfiguration Configuration { get; } // This...

this is my /$odata endpoint: ```C# Api.Controllers.TenantsController.Get (Api) | GET | Tenants Api.Controllers.TenantsController.Get (Api) | GET | Tenants/$count Api.Controllers.TenantsController.Get (Api) | GET | Tenants({key}) Api.Controllers.TenantsController.Get (Api) | GET | Tenants/{key}...

Yes, that would be great, I think its common to people to like to serve camelcase json properties and a the same time use the c# method naming convention pascalcase.

Just tried today, got the same error, this project seems pointless if I have to deal with all the bullshit that comes with setting up vim.

Really need this. Cant really build price tables without showing features. And the option to build pricing tables from the dashboard does not seems to work with firebase.

After wasting a week on the old version of the sdk, came to this. So should just throw this extension in the garbage? I mean, if we cant even simple...

.responseObject(completionHandler: { (response: DataResponse) in Should work.