-
Notifications
You must be signed in to change notification settings - Fork 50
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
Making the UI as an extension point as well #204
Comments
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. |
* feat:添加adguardhome、memcached、qiandao、lsky-pro、bitwarden、rustdesk、synapse * feat:添加cloudreve、nginx-proxy-manager、code-server
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 serval extension points:
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
, andwebSocket
might be very different with each other.Suggested extension points might be:
There are some potential solutions:
The text was updated successfully, but these errors were encountered: