[Studio] complete Message page service integration - #650
Open
Kris20030907 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Problem
The Message page uses a hard-coded Topic list, allows incomplete filters to reach the API, and reports simulated verification success instead of showing consumer status from the trace API.
Expected behavior
Topic options should come from the connected instance, each query mode should require its necessary filters, and message verification should display the trace API result.
Proposed fix
Load Topic options through
topicService, validate Topic/Key/Message ID inputs, prevent duplicate submissions, and open the consumer-status tab for verification.Follow-up
This change only completes the frontend service integration. The current backend providers are placeholders:
CloudMetadataProviderdoes not yet load Topics, whileMessageProviderStubreturns empty messages and traces. Querying an actual RocketMQ cluster should be implemented in a follow-up backend change.