Skip to content

feat: implement basic archive ui to make archiving failed versions easy #10182

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

Merged
merged 17 commits into from
Oct 11, 2023

Conversation

Emyrk
Copy link
Member

@Emyrk Emyrk commented Oct 10, 2023

I recognize the "reload" is not good, and this does not expose all functionality such as "unarchive". I will defer some styling and that for now to the FE team.

The CLI has all the functionality needed, the UI has the easy ability to hide "failed" versions, which is the primary reason for the feature.

Peek.2023-10-10.11-26.webm

@Emyrk Emyrk force-pushed the stevenmasley/archive_ui branch from a7129f0 to 2a1f3ee Compare October 10, 2023 16:30
onError: (error) => {
displayError(getErrorMessage(error, "Failed to archive version"));
},
});
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All the queries and mutations we are putting into the api/queries modules

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just copy pasted what was above, and changed it to archive vs promote.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we refactor this in another PR?

I think I need to learn this new style of pushing the mutation to an external package. I thought it would be a copy paste, but it is not.

The current code is async and works on useState and callbacks, but it seems the new way is to await?

Copy link
Collaborator

@BrunoQuaresma BrunoQuaresma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a few things would be better to be resolved before merging. Let me know if you are ok with doing them or want me to do that 😁

@Emyrk
Copy link
Member Author

Emyrk commented Oct 11, 2023

@BrunoQuaresma I will fix your suggestions. also feel free to make any changes you'd like to.

Base automatically changed from stevenmasley/archive_api_cli to main October 11, 2023 14:26
@Emyrk Emyrk enabled auto-merge (squash) October 11, 2023 14:56
@Emyrk Emyrk merged commit ac623b4 into main Oct 11, 2023
@Emyrk Emyrk deleted the stevenmasley/archive_ui branch October 11, 2023 15:06
@github-actions github-actions bot locked and limited conversation to collaborators Oct 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants