rails-api

It would be nice to somehow register the default fields that should be on response for each resource.
This would avoid repetitive includes and decrease the payload.

As of right now, CircleCI fails due to the fact that it was never updated to correctly test whether or not the API code works. Somebody should rewrite the CircleCI code and make it work again.

rails-api

Here are 638 public repositories matching this topic...

asyraffff / Open-Source-Ruby-and-Rails-Apps

zauberware / rails-devise-graphql

rootstrap / rails_api_base

Gokul595 / api_guard

jordifierro / rails-api-base

igorkasyanchuk / fake_api

rootstrap / active-storage-base64

lifeiscontent / realworld

johncorderox / Rails-API-React-Tutorial

adaam2 / docker-rails-react-starter

dannyyu92 / barebones

danielmoralesp / guias-de-rails-espanol

victor-am / rails-ranger

codemy / invoiced

autoforce / APIcasso

Default fields to be on responses

codica2 / timebot

PacktWorkshops / The-Ruby-Workshop

pavelkvasnikov / endpoint-flux

codica2 / rest-graphql

hayfever / sorcery-jwt

falko-org / Falko-API

guillaumebriday / rails-vue-cli

ezekg / example-rails-api-key-authentication

huobazi / vuejs-with-rails-api-and-jwt-example

ghoshnirmalya / linkedin-clone-rails-backend

stuyspec / stuyspec-api

Fix CircleCI errors

Passing in a String[] of Roles

yocosaka / Tracking-App-Api-with-Rails

npetkov / auth0_rails_api_example

hdf1986 / querifier

nejdetkadir / google-keep-api

Improve this page

Add this topic to your repo