[IMPLEMENTED] Simple Graphql & Graphql Explorer

NeoMoritsiqu · February 27, 2021, 9:33pm

Hi Sebastian,

I wanted to give an example from Graphcms.
The editor here is very good. The Explorer tab works very well.

Also the system’s graphql output is very clean.
It does not add additional wrappers such as (“flatData”, “iv”).

It would be great if things were like this with Squidex.

Sebastian · February 28, 2021, 12:28pm

Hi,

we can switch to a another graphql UI, such as https://github.com/graphql/graphql-playground, but I don’t want to change the data format as it makes things more complicated when the different between events / REST / graphql and so on differs too much.

NeoMoritsiqu · February 28, 2021, 12:36pm

Hi Sebastian,

First of all, thank you for your interest. I think it would be very useful to switch to this editor, which provides more possibilities. But I think you should consider making improvements on the data side as well. Modeling expressions such as “flatData, data, queryContents” on the client side is very difficult and takes an ugly dimension. It should be much simpler. we love you and your support. thanks.

Sebastian · February 28, 2021, 12:54pm

Hi, there is also Banana Cake Pop, not sure yet what is the best.

What is your concrete suggestion for data, I know that the extra dimension sucks, but what is the alternative? If you make it flat you can have consistency issues with the naming, so you have at least to add an extra query with a new model.

Sebastian · March 2, 2021, 5:01pm

I am not sure what exactly you expect from the new UI.

NeoMoritsiqu · March 2, 2021, 6:33pm

At the same time, I think it is necessary to improve the results of the queries. Maybe here we can think together and produce a better result. Existing outputs require us to produce additional internal classes while creating GraphqlRequestModel and GraphqlResponseModel both in terms of traffic and client side. For example: like “flatData” or “iv”.

Thanks for your support

Sebastian · March 2, 2021, 8:44pm

As I said, this is out of scope.

There are several reasons for that:

Every new type costs memory. It is really sums up and I have added a lot of improvements already to keep that low. This is also the reason why I have not moved to HotChocolate yet, which is in my opinion the better GraphQL library: https://github.com/ChilliCream/hotchocolate/issues/3012
When moving everything from flatData to the root level, the meta fields like id and so on have to be moved to a sub property to avoid conflicts, like __meta or so (even “meta” is not safe).
When the different models between rules, scripts, REST and graphql differ too much I have a hard time explaining that.

NeoMoritsiqu · March 2, 2021, 8:50pm

Actually, I can guess, very radical changes are required. But how does it work on other cms? Products such as GraphCMS and Strapi produce very successful outputs.

Sebastian · March 2, 2021, 9:02pm

For example GraphCMS does not let you create a field with name “id”. I am not sure if this is the best decision they have made, because they will have a hard time when introducing new meta fields.

In general I would say you have these options:

Prefix custom fields (as done in Squidex)
Prefix meta fields with nested object. Because of backwards compatibility we would have to use something like __meta.id or so.
Block some fields (cannot be done later anymore, therefore sucks)
Prefix meta fields (e.g. with __ or so). Sucks because in Javascript and other dynamic languages you usually do not have a deserializer.

So for me only 1 and 2 would work, so what is the point by moving from 1 to 2?

Sebastian · March 2, 2021, 9:24pm

Interesting: https://foundation.graphql.org/news/2020/04/03/web-based-graphql-ides-for-the-win-how-why-playground-graphiql-are-joining-forces/

I can probably migrate to GraphQL Playground and then later to GraphiQL 2.0. Should hopefully not thate more than 1-2 hours. Will do it tomorrow.

NeoMoritsiqu · March 2, 2021, 9:47pm

Super news. We are waiting for your good news.

Sebastian · March 3, 2021, 1:44pm

I had a closer look. GraphCMS uses GraphiQL as well with a few adjustments. Together with this library. But even the demo looks very clunky, so it takes a lot of effort to integrate everything properly. Not on my roadmap at the moment.

But there is an example and relatively easy to implement with a PR (I hope)

github.com

OneGraph/graphiql-explorer-example/blob/master/src/App.js

// @flow

import React, { Component } from "react";
import GraphiQL from "graphiql";
import GraphiQLExplorer from "graphiql-explorer";
import { buildClientSchema, getIntrospectionQuery, parse } from "graphql";

import { makeDefaultArg, getDefaultScalarArgValue } from "./CustomArgs";

import "graphiql/graphiql.css";
import "./App.css";

import type { GraphQLSchema } from "graphql";

function fetcher(params: Object): Object {
  return fetch(
    "https://serve.onegraph.com/dynamic?app_id=c333eb5b-04b2-4709-9246-31e18db397e1",
    {
      method: "POST",
      headers: {

This file has been truncated. show original

Sebastian · March 5, 2021, 9:00pm

Btw. What do you think about this one?

NeoMoritsiqu · March 6, 2021, 7:13pm

Hi Sebastian,

The company I work for is also very intense in our own development plans. There is a huge increase in our business due to the pandemic. Therefore, I want to be interested if I get the opportunity. Actually, this is a need, but I believe that you can develop such things much faster because you have more information on the system than I do. But since I know what it means to develop open source software, it doesn’t feel right to expect everything from you. I wish my whole day was free and I could develop something together.

Sebastian · March 6, 2021, 8:28pm

Sorry, I have forgotten the link. I wanted to ask:

"What do you think about this one: “https://chillicream.com/docs/bananacakepop”?

Unfortunenalty it is also impossible to integrate at the moment. I will postpone this feature request and wait until something pops up.

system · February 10, 2023, 9:21pm

This topic was automatically closed after 2 days. New replies are no longer allowed.