Making the UI as an extension point as well
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:
This issue has been open 30 days with no activity. This will be closed in 7 days.
This issue has been automatically marked as stale because it hasn't had any recent activity.If you think this should still be open, or the problem still persists, just pop a reply in the comments and one of the maintainers will (try!) to follow up. Thank you for your interest and contribution to the api-testing.
This issue has been open 30 days with no activity. This will be closed in 7 days.
This issue has been open 30 days with no activity. This will be closed in 7 days.
This issue has been automatically marked as stale because it hasn't had any recent activity.If you think this should still be open, or the problem still persists, just pop a reply in the comments and one of the maintainers will (try!) to follow up. Thank you for your interest and contribution to the api-testing.
Now we have several UI extensions:
- https://github.com/LinuxSuRen/atest-ext-store-database
- https://github.com/LinuxSuRen/atest-ext-store-terminal
- https://github.com/LinuxSuRen/atest-ext-store-mermaid
- https://github.com/LinuxSuRen/atest-ext-store-math
By the way, below PR implemented a very basic API proxy for the extension:
https://github.com/LinuxSuRen/api-testing/pull/858