• fix: use dynamic parameter resolution in the cli #21734
• feat: add endpoint to fetch singular org member #21732 👈 (View in Graphite)
• chore: move List util out of db2sdk to avoid circular imports #21733
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Documentation Check

No Changes Needed

This PR adds a new API endpoint GET /organizations/{organization}/members/{user} to fetch a single organization member. The API documentation in docs/reference/api/members.md appears to be auto-generated from OpenAPI annotations in the Go code (as evidenced by the @Summary, @ID, @Tags, and @Router annotations in the handler).

The PR includes proper OpenAPI annotations for the new getOrganizationMember handler, which means the API documentation will be automatically updated when the docs are regenerated (likely via make gen or similar command).

No manual documentation changes are needed for this change.

Automated review via Coder Tasks

Documentation Check

Previous Feedback

The previous review correctly noted that API documentation is auto-generated from OpenAPI annotations.

Updates Needed

• coderd/members.go line 150 - Fix OpenAPI annotation for getOrganizationMember handler

The @Success annotation currently shows 204 but the handler actually returns http.StatusOK (200) with JSON data. It should be:

// @Success 200 {object} codersdk.OrganizationMemberWithUserData

This will ensure the auto-generated API documentation correctly shows the response format for the new GET /organizations/{organization}/members/{user} endpoint.

Automated review via Coder Tasks

Documentation Check

Previous Feedback

Not yet addressed - the OpenAPI annotation issue identified in the previous review remains unfixed.

Updates Needed

• coderd/members.go line 153 - Fix OpenAPI annotation for getOrganizationMember handler

The @Success annotation still shows 204 but the handler returns http.StatusOK (200) with JSON data on line 189. It should be:

// @Success 200 {object} codersdk.OrganizationMemberWithUserData

This will ensure the auto-generated API documentation correctly shows the response format for the new GET /organizations/{organization}/members/{user} endpoint.

Automated review via Coder Tasks

Documentation Check

Previous Feedback

Not yet addressed - the OpenAPI annotation issue identified in previous reviews remains unfixed.

Updates Needed

• coderd/members.go line 153 - Fix OpenAPI annotation for organizationMember handler

The @Success annotation currently shows 204 but the handler returns http.StatusOK (200) with JSON data on line 191. It should be:

// @Success 200 {object} codersdk.OrganizationMemberWithUserData

This will ensure the auto-generated API documentation correctly shows the response format for the new GET /organizations/{organization}/members/{user} endpoint.

Automated review via Coder Tasks

Documentation Check

Previous Feedback

Not yet addressed - the OpenAPI annotation issue identified in previous reviews remains unfixed in the latest commits.

Updates Needed

• coderd/members.go line 150 - Fix OpenAPI annotation for organizationMember handler

The @Success annotation currently shows 204 but the handler returns http.StatusOK (200) with JSON data (line 191 in the implementation: httpapi.Write(ctx, rw, http.StatusOK, resp[0])).

It should be:

// @Success 200 {object} codersdk.OrganizationMemberWithUserData

This will ensure the auto-generated API documentation in docs/reference/api/members.md correctly shows:

• Status 200 instead of 204
• The response schema for OrganizationMemberWithUserData
• Example response body showing the member object structure

After fixing the annotation, run make gen to regenerate the Swagger docs and API reference documentation.

Automated review via Coder Tasks

Documentation Check

Previous Feedback

Not yet addressed - the OpenAPI annotation issue identified in previous reviews remains unfixed.

Updates Needed

• coderd/members.go line 153 - Fix OpenAPI annotation for organizationMember handler

The @Success annotation currently shows 204 but the handler returns http.StatusOK (200) with JSON data (see line 191: httpapi.Write(ctx, rw, http.StatusOK, resp[0])).

It should be:

// @Success 200 {object} codersdk.OrganizationMemberWithUserData

This will ensure the auto-generated API documentation correctly shows:

• Status code 200 instead of 204
• The response schema for the returned member object
• Example response body structure

After fixing the annotation, run make gen to regenerate the API documentation.

Automated review via Coder Tasks