wso2 / wso2/api-platform

Implement Frontend Support for API Spec Change During Publish to Developer Portal

Open
#260 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area/Management Type/UX
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Current Behavior

Currently, the Management Portal frontend does not support updating or changing the API specification when publishing an API to the Developer Portal.
The backend (Platform API) does not yet provide endpoints to accept API specification updates during publishing.

Proposed Frontend Changes

  • Implement UI components to allow users to upload API spec before publishing.
  • Integrate with Platform API once backend support is available:
    • Send updated API spec as part of the publish request.
    • Handle success/failure responses and display appropriate feedback in the UI.

Dependencies

  • Requires backend (Platform API) support to accept API spec changes during publishing.
  • Frontend implementation should be ready to integrate once the API is available.

Benefits

  • Enables users to update API spec at publish time without separate steps.
  • Improves workflow efficiency when publishing APIs to Developer Portal.
  • Ensures consistent API spec management across frontend and backend.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Management Portal's API publishing flow and reviewing the Platform API publish contract once backend support is available. Confirm the upload, request, and success or failure behavior with the backend team; done means the frontend can submit an updated API specification during publishing and display the resulting feedback.

Written by the indexing model from the issue text.

Assessment

Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.