Adding to dev portal failed when the Sandbox Endpoint is null
Open
Nobody has claimed this yet.
Area/DeveloperPortal
Priority/High
Severity/Major
Type/Bug
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
The sandbox endpoint of an API should be optional. Not every API will have a sandbox endpoint.
Steps to Reproduce
- From the management portal, try to add an API to the developer portal
- Go to "More Settings" and remove the sandbox endpoint
- Now try to add the API to the developer portal.
- It'll show an Internal Server Error. Please note that I didn't notice any backend logs too (maybe I didn't check correctly). But if logs are missing there is a big problem in the code.
Environment Details (with versions)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the management-portal flow with the sandbox endpoint removed, then trace how the add-to-developer-portal request handles the missing value. Done means an API without a sandbox endpoint can be added successfully and the failure is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100