LinuxSuRen / LinuxSuRen/api-testing
Making the UI as an extension point as well
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Now, we have serval extension points:
- storage
- secret
Actually, providing UI extension is also very important. Different protocals have different elements, it's better to load the corresponding page instead of putting all things together. For example, gRPC, HTTP, and webSocket might be very different with each other.
Suggested extension points might be:
- [UI] Store editing and creating page
- [UI] TestCase page
There are some potential solutions:
Contributor guide
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 reviewing the proposed UI extension points for the Store editing/creating page and TestCase page, along with the linked Vue SSR discussion. Define how protocol-specific pages for gRPC, HTTP, and WebSocket would be loaded and what extension boundaries are required; the issue is done when those UI extension points are specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100