Jump to content

icepuma

Member
  • Posts

    3
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Profile Information

  • Gender
    Male
  • Location
    Berlin / Germany
  • Occupation
    Scala Developer
  1. Treat your code like you would treat an essay. Just be as descriptive as you can. Don't name a variable "a", don't be short! Write meaningful method names.
  2. You can entirely get rid of the "race_" in every key: { "races": [ { "title": "", "id": "", "active": true, "description": "", "map": { "enabled": false, "source": "" }, "image": { "enabled": true, "source": "" } "color": { "enabled": false, "color": "rgba(255,255,255)" } } ], "count":1 } And better be more descriptive, like "description" instead of "desc"
  3. The upper "domain model" is much simpler in terms of marshalling / unmarshalling. If the "extra" part given in the second example isn't necessary for the first call, then you could do some deeplinking. But if everything belongs together, I personally would stick to the first example. Edit: Since facebook got a better licensing for graphql you could look for that. Then you could decide on the client side, what info you need.
×