adobe / commerce-cif-graphql-integration-reference Goto Github PK

This code is not supported by any team at Adobe, but it still bears our name. This can be confusing to developers, and when things don't work (and they won't) we still have to support them. Best to archive to send a clear signal that this code should NOT be used, or only for reference.

Expected Behaviour

Running the aio deploy command should deploy the code successfully.

Actual Behaviour

Unable to deploy the code via Windows system into Adobe IO
we get below error

Reproduce Scenario (including but not limited to)

Steps to Reproduce

1. Clone the repo.
2. Follow the instructions to deploy as per Readme.MD file.
3. we get the error.

Platform and Version

System : windows
Version : latest

Sample Code that illustrates the problem

Logs taken while reproducing problem

@cjelger

Getting below error while using Product List commerce OOTB component.

QUERY should basically resolve on below mentioned resolver only, right ?

Expected Behaviour

After running npm run deploy command project should deploy successfully

Actual Behaviour

After running npm run deploy command i am getting below error
Serverless Error ---------------------------------------

Failed to deploy package (graphql-reference) due to error: PUT https://adobeioruntime.net/%0D/api/v1/namespaces/51906-cifintegration/packages/graphql-reference?overwrite=true Returned HTTP 405 (Method Not Allowed) --> "Response Missing Error Message."

Reproduce Scenario (including but not limited to)

Steps to Reproduce

run npm run deploy
2020-08-10T07_23_09_198Z-debug.log
2020-08-10T07_28_24_911Z-debug.log

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Hi Team,

While trying to make a call to Magento Graphql from AdobeIO Action NodeJS code. It doesn't return the response to the endpoint of AdobeIO runtime. But it works absolutely fine. If we do a REST call and get the response the data from AdobeIO runtime.

NOTE: we are getting the response from Magento in Adobe IO Node JS. But Adobe IO runtime response produces null.

Reference Community thread : https://experienceleaguecommunities.adobe.com/t5/adobe-i-o-runtime-questions/invoke-graphql-query-from-adobe-io/qaq-p/382168

Expected Behaviour

No typos. GraphQL is written as GraphiQL.

Actual Behaviour

GraphQL is written as GraphiQL

Reproduce Scenario (including but not limited to)

Search for 'graphiql' in README.md

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Was trying out the reference project and setup on Adobe IO Runtime.

I have following Raw json response from Magento GraphQl, similarly I want it from Adobe IO endpoint.

How we use it in place of already existing RAW JSON ?
{
"data": {
"products": {
"items": [
{
"__typename": "ConfigurableProduct",
"id": 278,
"color": null,
"sku": "SKUID01",
"name": "Mountain Kit",
"description": {
"html": "

Description

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency @adobe/aio-lib-state to v1.1.3
• Update external fixes (@openwhisk/wskdebug, adobe/aio-apps-action, adobe/aio-cli-setup-action, axios, chai, core-js, eslint-plugin-react, graphiql, inquirer, regenerator-runtime)
• Update adobe major (major) (@adobe/aio-lib-state, @adobe/aio-sdk, @adobe/exc-app)
• Update external major (major) (actions/checkout, actions/setup-node, adobe/aio-apps-action, axios, chai, chalk, dataloader, eslint, graphiql, graphql, graphql-tools, inquirer, mocha, mocha-junit-reporter, node, react, react-dom, sinon)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

As the code is deployed in Adobe IO point and AEM picks up the data as graphql request from endpoint.
How do we verify the console logs in Node Loader JS file. It doesn't logs as part of chrome logs