some observations / enhancement request

@raymondfeng

Thanks for sharing this example.

I tried using your example code and have a few observations that I would like to share with you.

1. I think we should make "offset" a user input.
2. For the case when input "limit" is greater than the number of messages within the selected topic, the explorer is stuck in "Loading" state. I can see that it gets the messages from the backend, but since the messages are less than the requested limit, it just sits there for a timeout to occur and eventually error's out.

Please let me know your thoughts.

Based on your feedback, I am looking forward to add a few things to this example and will be happy to share an updated version with the community.

BTW I am using the latest versions of the following packages.
"@loopback/authentication": "^5.0.0",
"@loopback/authentication-jwt": "^0.5.0",
"@loopback/authorization": "^0.6.4",
"@loopback/boot": "^2.4.1",
"@loopback/core": "^2.9.3",
"@loopback/extension-health": "^0.4.11",
"@loopback/extension-metrics": "^0.3.11",
"@loopback/repository": "^2.11.0",
"@loopback/rest": "^6.0.0",
"@loopback/rest-crud": "^0.8.11",
"@loopback/rest-explorer": "^2.2.8",
"@loopback/service-proxy": "^2.3.6",
"kafka-node": "^5.0.0",

Commencez par le code d’exemple et suivez la manière dont offset et limit sont transmis via l’explorer au backend pour un sujet sélectionné. Vérifiez le comportement lorsque moins de messages sont renvoyés que le limit demandé, et confirmez que offset est exposé comme entrée utilisateur et que le chargement se termine sans attendre un timeout.