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

Create loading state for save buttons on forms related to projects #1574

Open
3 of 5 tasks
Spiteless opened this issue Feb 4, 2024 · 4 comments
Open
3 of 5 tasks

Comments

@Spiteless
Copy link
Member

Spiteless commented Feb 4, 2024

Dependency

This issue should be delayed until #1576 is solved due to potential merge conflicts

Overview

Set save button to spinning loading icon while waiting for database to reply

Action Items

  • Edit ProjectForm component save button to be disabled and show a loading icon to the user.
    • Model this state off of the ReadyEvents file
    • Update submitNewProject and submitEditProject to initialized loading state when called and end loading state when returned or caught error.
  • QA
  • When complete, go to Epic: Project Edit Save #1598 and mark the checkbox referencing this issue as complete.
@github-actions github-actions bot added this to New Issue Approval in VRMS - Active Project Board Feb 4, 2024
@Spiteless Spiteless added role: Front End size: 2pt Can be done in 7-12 hours labels Feb 4, 2024
@Spiteless Spiteless added this to the 04.01 Existing Features milestone Feb 4, 2024
@Spiteless Spiteless moved this from New Issue Approval to Prioritized Backlog in VRMS - Active Project Board Feb 4, 2024
@Spiteless
Copy link
Member Author

This issue should be delayed until #1576 is solved due to potential merge conflicts

@JackHaeg
Copy link
Member

JackHaeg commented May 7, 2024

@josiehandeveloper when you have a moment, can you please provide an update on this issue with teh following information below?:

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
  • remember to add links to the top of the issue if they are going to be needed again.

@josiehandeveloper
Copy link
Member

  1. Progress: It's in progress
  2. Blockers: I'm having trouble figuring out the logic to communicate to the backend
  3. Availability: I'll have 3 hours to work on this
  4. ETA: Hopefully soon

@JackHaeg
Copy link
Member

JackHaeg commented May 7, 2024

Unassigning for now, moving back to prioritized backlog.

@JackHaeg JackHaeg moved this from In progress to Prioritized Backlog in VRMS - Active Project Board May 7, 2024
@lcchrty lcchrty self-assigned this May 14, 2024
@lcchrty lcchrty moved this from Prioritized Backlog to In progress in VRMS - Active Project Board May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

When branches are created from issues, their pull requests are automatically linked.

4 participants