Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: derive workspace status on backend#4284

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
f0ssel merged 3 commits intomainfromf0ssel/workspace-status
Sep 30, 2022
Merged

Conversation

f0ssel
Copy link
Contributor

@f0sself0ssel commentedSep 30, 2022
edited
Loading

I wanted to just knock this out while I had the time so I went ahead but would like to explain my work here for learning purposes. Going through each commit should tell the story of my process.

  1. a71547e - I added the new types to thecodersdk package, added thestatus field to theworkspace type, and ranmake gen to generate the ts client as well.
  2. de9623d - I knew we had aconvertWorkspace function that took a few different DB objects and made acodersdk.Workspace for api responses. I also knew that the status was completely derived from the workspace build, which is already passed into this conversion function. I added the logic there and some tests for it that at least cover the states at rest.

Note I changed the statestarted torunning in this case since it matched what we display and made more sense to me. I also did the same with changingerror tofailed. These changes made more sense to me as a consumer.

I'm going to leave the frontend changes for another PR to keep this simple and easy to read.

@f0sself0ssel marked this pull request as ready for reviewSeptember 30, 2022 21:00
@f0sself0ssel requested a review froma team as acode ownerSeptember 30, 2022 21:00
@f0sself0ssel requested review frompresleyp anda team and removed request fora teamSeptember 30, 2022 21:00
@f0sself0sselenabled auto-merge (squash)September 30, 2022 21:06
Copy link
Contributor

@presleyppresleyp left a comment

Choose a reason for hiding this comment

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

I actually followed that, thanks! Looks great, I agree with updating the wording.

f0ssel reacted with rocket emoji
@f0sself0ssel merged commit139bc6f intomainSep 30, 2022
@f0sself0ssel deleted the f0ssel/workspace-status branchSeptember 30, 2022 21:36
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@presleyppresleyppresleyp approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@f0ssel@presleyp

[8]ページ先頭

©2009-2025 Movatter.jp