Save Snippet Button Not Working / Loading State Not Updating

[chiscookeke11]

Description

When clicking the "Save Snippet" or "Update Snippet" button in the Snippets page, nothing happens. The form does not submit properly, and the loading state (loading) does not show while the API request is in progress. This makes it unclear to the user whether the action was successful or if something went wrong.

Expected Behavior

• Clicking Save Snippet should submit the form and save the snippet via the API.
• While saving, a loading indicator should appear to indicate that the request is in progress.
• After a successful save:
  • The form should close
  • The snippet list should refresh to include the new/updated snippet
• Errors should be displayed if the API request fails.

Current Behavior

• Clicking the button sometimes does nothing
• No loading feedback is shown
• The snippet list may not refresh correctly
• The form does not always close on successful submission

Suggested Fix

• Ensure the onSubmit function is properly awaited and errors are caught.
• Update loading state or add a separate saving state to show a loading spinner or disable the submit button while the request is in progress.
• After successful save, call fetchSnippets() to refresh the list and closeForm() to reset the form.
• Consider disabling the submit button during the save to prevent multiple submissions.

Acceptance Criteria

• Clicking Save Snippet / Update Snippet triggers the API request.
• A loading state (spinner or disabled button) is visible while saving.
• Snippet list refreshes automatically after saving.
• Form closes after successful save.
• Errors are handled and displayed to the user if saving fails.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I will like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Obiajulu-gif to this issue.

[Elite-tch]

@Elite-tch has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I will like to work on this issue ETA 12hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Elite-tch to this issue.

[drips-wave]

Congratulations, @Elite-tch! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Elite-tch: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊