Skip to content
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

Implement updateSubmission mutation into the modSubmissionStore #801

Open
2 tasks done
NabbeunNabi opened this issue Oct 10, 2024 · 0 comments
Open
2 tasks done

Implement updateSubmission mutation into the modSubmissionStore #801

NabbeunNabi opened this issue Oct 10, 2024 · 0 comments
Assignees
Labels

Comments

@NabbeunNabi
Copy link
Contributor

NabbeunNabi commented Oct 10, 2024

Problem

We want all our API calls for data management to be stored in their respective stores. Currently this is being done within the file itself. This should be moved into a store.

Success

The functionality of the updateSubmission is moved into the modSubmissionStore

Requirements

  • Move the API call for the graphQL mutation into the modSubmissionStore
  • Use this refactored mutation call within the form itself.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants