Utils for constructing v2 mutations #125
Conversation
| @@ -15,7 +15,7 @@ | |||
| "scripts": { | |||
| "build": "tsc -p src", | |||
| "clean": "rm -rf lib node_modules out", | |||
| "fix": "npm run lint -- --fix && npm run pretty", | |||
| "fix": "npm run lint -- --fix", | |||
There was a problem hiding this comment.
npm run pretty messes stuff up so that it no longer passes lint... maybe its only an issue for me? If not, should I remove the pretty command as well?
|
Let me know if you think these would be helpful to include for people trying to build v2 mutations. |
There was a problem hiding this comment.
@willmarks can you provide some sort of example usage in the form of docs or test?
| key: { | ||
| uid: '<cicd_Build>', | ||
| pipeline: qb.ref(pipeline), | ||
| }, | ||
| body: { | ||
| name: '<build_name>', | ||
| }, |
There was a problem hiding this comment.
The reason for the separation of key and body was so we could only write the key fields in the situation where the model is a reference and should only result in phantom if the model is not already there. If we don't mind phantoms having non-key fields populated (e.g. build.name being populated) we could combine the key and body objects into a fields object that contained all fields.
|
Kudos, SonarCloud Quality Gate passed!
|
Description
Some helpers when constructing v2 mutations.
Type of change