-
Notifications
You must be signed in to change notification settings - Fork 1
CRDCDH-3025 Remove deleteApplication GraphQL alias
#770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRDCDH-3025 Remove deleteApplication GraphQL alias
#770
Conversation
Pull Request Test Coverage Report for Build 16198722036Details
💛 - Coveralls |
Co-authored-by: amattu2 <38357871+amattu2@users.noreply.github.com>
Co-authored-by: amattu2 <38357871+amattu2@users.noreply.github.com>
Good catch! I've removed the redundant field alias since the mutation name and field name are now the same. The GraphQL query now uses the cleaner syntax: |
deleteApplication GraphQL alias
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Summary
Updates the frontend GraphQL query to use the new
cancelApplicationmutation instead ofdeleteApplicationto align with the backend API renaming.Background
The backend GraphQL API has renamed the mutation from
deleteApplicationtocancelApplication. This change updates the frontend to use the correct mutation name.Changes Made
src/graphql/cancelApplication.tscancelApplicationinstead ofdeleteApplicationin the GraphQL mutationcancelApplication: deleteApplication(_id: $_id, comment: $comment)cancelApplication: cancelApplication(_id: $_id, comment: $comment)Technical Details
CANCEL_APPfrom the GraphQL module will automatically use the updated mutationVerification
deleteApplicationexist in the codebaseReference
Jira ticket: CRDCDH-3025
This pull request was created as a result of the following prompt from Copilot chat.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.