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

GSOC is triplicated in Bee API sidebar #4967

Closed
Cafe137 opened this issue Jan 29, 2025 · 2 comments · Fixed by #4989
Closed

GSOC is triplicated in Bee API sidebar #4967

Cafe137 opened this issue Jan 29, 2025 · 2 comments · Fixed by #4989
Assignees

Comments

@gacevicljubisa
Copy link
Contributor

gacevicljubisa commented Feb 4, 2025

This is beacuse we have 3 tags for this endpoint

bee/openapi/Swarm.yaml

Lines 837 to 843 in cda61e5

"/gsoc/subscribe/{address}":
get:
summary: Subscribe to GSOC payloads
tags:
- GSOC
- Subscribe
- Websocket

Do we remove 2 tags, or we add this tags for some other endpoints to group with them as well?
@NoahMaizels

@NoahMaizels
Copy link
Contributor

Do we remove 2 tags, or we add this tags for some other endpoints to group with them as well? @NoahMaizels

Yeah I think I did exactly like you mentioned and it fixes it, I just did this for the docs repo and am gonna merge it, will you guys do it for the OpenAPI specs in the Bee repo?

"/gsoc/subscribe/{address}":
    get:
      summary: Subscribe to GSOC payloads
      tags:
        - GSOC
      parameters:
        - in: path
          name: reference
          schema:
            $ref: "SwarmCommon.yaml#/components/schemas/SwarmReference"
          required: true
          description: "Single Owner Chunk address (which may have multiple payloads)"
      responses:
        "200":
          description: Returns a WebSocket with a subscription for incoming message data on the requested SOC address.
        "500":
          $ref: "SwarmCommon.yaml#/components/responses/500"
        default:
          description: Default response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants