graphql-api

GraphQL is a data query language developed by Facebook. It provides an alternative to REST and ad-hoc webservice architectures. It allows clients to define the structure of the data required, and exactly the same structure of the data is returned from the server. It is a strongly typed runtime which allows clients to dictate what data is needed.

Issue Description

Since the old Instagram API will stop working on June 29 (See https://www.instagram.com/developer/), the url in https://github.com/parse-community/parse-server/blob/d0a9c709fea4cbdba540420353a36a0e89601ffb/src/Adapters/Auth/instagram.js#L9 needs to be changed to match the new "instagram_graph_user_profile" API. (See https://developers.facebook.com/docs/instagram-basic-disp

Description
To be able to optionaly remove the google fonts dependency on any page of the api-platform.

Example
Remove the google font stylesheet in line 8 in the file api-platform\core\src\Bridge\Symfony\Bundle\Resources\views\SwaggerUi\index.html.twig depending on a configuration variable.

Context
I'm working on an intranet application for a 100000+ employees company and

Currently, in order to register a field to an Edge you have to know the full Edge name, like RootQueryToPostConnectionEdge and that's cumbersome.

It would be nice to have something like: register_graphql_edge_field( $fromType, $toType, $fieldName, $config );

I think it's easier to know the from/to type than know the fully qualified edge name.

We have types in various places that do not follow the Rust naming conventions. A good example are all the GraphQL* types that should be spelled GraphQl* to follow the conventions.

It would be nice to clean this up by renaming all types that don't follow the rules.

Marking this as a "good first issue", as it's low-hanging fruit and would be a good way for new contributors to contribute somet

What is the motivation for adding / enhancing this feature?

There is an object product_links that needs to be mapped to the `vsf-catalo

Jul	AUG	Sep
	29
2019	2020	2021

graphql-api

Here are 311 public repositories matching this topic...

parse-community / parse-server

Issue Description

graphile / postgraphile

api-platform / api-platform

postlight / headless-wp-starter

ardatan / graphql-tools

kriasoft / nodejs-api-starter

wp-graphql / wp-graphql

dbohdan / automatic-api

daptin / daptin

leangen / graphql-spqr

graphprotocol / graph-node

gentics / mesh

afuh / rick-and-morty-api

prismake / typegql

spikenail / spikenail

Shpota / skmz

morpheusgraphql / morpheus-graphql

graphqlize / graphqlize

sergiodxa / grial

vuex-orm / plugin-graphql

Canner / gqlify

Novvum / 36-graphql-concepts

wittydeveloper / react-apollo-form

DivanteLtd / storefront-api

What is the motivation for adding / enhancing this feature?

leangen / graphql-spqr-spring-boot-starter

dabit3 / aws-appsync-react-workshop

prabhuomkar / frisky

GraphQL-Party / HangZhou-GraphQL-Party

zauberware / rails-devise-graphql

sisense / graphql2rest

Related Topics