Using keys as parameters in GraphQL

[Petr_Plenkov]

I am referring to URL:

https://cap.cloud.sap/docs/releases/nov21#graphql-adapter-for-nodejs-experimental

Hi! Great job on GraphQL - so much more things we can do now. Just as a feedback - could you please add keys also to input parameters?

Now only filters are available and is not really convenient:

Thank you!

[vansyckel]

Hi pepl.booking,

Thanks for the feedback!

Could you please provide some more information on what you are looking for? GraphQL filters become SQL where clauses and it shouldn't make a difference whether it's a key property or not, right?

Thanks and best,
Sebastian

[Petr_Plenkov]

Hi Sebastian!

Well is only to make queries more dev friendly. One big reason for us to move to graphQL from Odata queries is to avoid constructing these multiple $select, $filter and $expand constructions. So in the end I expect to have something like this:

query getParentPipeline($CI_PROJECT_PATH: ID!, $CI_PIPELINE_IID: ID) {
  project( fullPath: $CI_PROJECT_PATH ) { 
    id       
    fullPath
    pipeline(iid: $CI_PIPELINE_IID){      
      upstream {
        id     
        ref
        status
        active     
        project {
          id          
          fullPath
        }        
      }
    }
  }  
}

In Odata such URL would look way less readable.

Meanwhile could you please give some highlights? Is it transforming directly to SQL or still using Odata as intermediate level?

Thank you!

Regards

Petr

[Petr_Plenkov]

May be in the end we can have some special GraphQL annotations like @graphql.searchable which will allow to search by some fields directly without filter, keeping that option only for complicated cases

[vansyckel · Accepted solution]

Hi pepl.booking,

OK, we'll take as a feature request. But please note that we have other short term priorities, so it could be a while.

The GraphQL query AST is converted to CQN.

Best,
Sebastian