Add decorateBaseSchema function qlkube

[ralls0]

Description

New function has been added. decorateBaseSchema function allow to change the dynamic schema create on the fly by qlkube. This new function uses five parameters:

• @param {*} targetQuery : Query wrapped int the extended object Type
• @param {*} extendedType : Object type that should be extended
• @param {*} argsNeeded : Arguments extracted from the father and passed from the wrapper
• @param {*} nameWrapper : Custom name for the wrapper
• @param {*} baseSchema : GraphQL Schema where the type and query are written

then a new GraphQLSchema object is returned.

How Has This Been Tested?

Below a test query used to test the new feature:

query test {
  itPolitoCrownlabsV1alpha2Instance (
    name: "green-tea-6831",
    namespace: "tenant-john-doe"
  )
  {
    spec {
      running
      templateCrownlabsPolitoItTemplateRef {
        name
        namespace
        templateWrapper{
          itPolitoCrownlabsV1alpha2Template {
            kind
            spec {
              prettyName
            }
          }
        }
      }
    }
  }
}

[kingmakerbot]

Hi @ralls0. Thanks for your PR.

I am @kingmakerbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch
• /merge: Merge this PR into the master branch
• /hold: Adds hold label to prevent merging with /merge
• /unhold: Removes the hold label to allow merging with /merge
• /deploy-staging: Deploy a staging environment to test this PR
• /undeploy-staging: Manually undeploy the staging environment

Make sure this PR appears in the CrownLabs changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[GabriFila]

I would provide an error in case the nameWrapper is not defined, as you did with targetQuery

[GabriFila]

The !== {} check will always result false, if you need this check you should use a loop with Obejct.keys. But I believe that a better approach would be to throw an error if the needed prop doesn't exist on the parent.

(also please remove the // gestire errori part)

[ralls0]

Being that argsNeeded is optional also newParent could be empty, isn't so?
May be Object.keys(newParent).length !==0 ? newParent : parent a good alternative?
I could add also a default value for the optional agrs.

[GabriFila]

@ralls0 thanks for the PR! 😍
I added few comments, also please edit the title of the PR and remove the testA,testB part from the PR description

[GabriFila]

/rebase

[GabriFila]

lgtm

[QcFe]

/lgtm

[giorio94]

/rebase

[GabriFila]

/deploy-staging

[kingmakerbot]

Your staging environment has been correctly deployed/updated!

• Current dashboard: check it out at https://454.staging.crownlabs.polito.it
• New frontend: check it out at https://454.staging.crownlabs.polito.it/app
• Frontend storybook: check it out at https://storybook.454.staging.crownlabs.polito.it
• qlkube: check it out at https://graphql.454.staging.crownlabs.polito.it
• Operators: add the 'crownlabs.polito.it/operator-selector=staging-454' label to your tenant

[GabriFila]

/merge

[GabriFila]

/merge

[kingmakerbot]

Your staging environment has been correctly teared-down!