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.
PR Checklist
If you have any questions, you can refer to the Contributing Guide
What is the current behavior?
The data is currently synchronized in one direction, Topic Tree -> Connections.
What is the new behavior?
This pull request includes several updates to the topic node and message services, as well as some minor changes to the SCSS and translation files. The main focus is on refactoring and enhancing the functionality related to topic tree structures and message statistics.
Enhancements to Topic Node and Message Services:
getMessageTopicNodeStats
method toMessageService
to fetch connection info and topic statistics.TopicNodeService
to improve the handling and retrieval of topic tree structures, including methods likegetTree
,updateTopicNodes
, andclearTree
. [1] [2] [3] [4] [5] [6] [7]buildTopicTreeFromStats
andflattenTopicTree
intopicTree.ts
for constructing and flattening topic trees.Minor Changes:
.text-tips
inatom.scss
.ImportScript.vue
.connections.ts
andviewer.ts
. [1] [2]Does this PR introduce a breaking change?
Specific Instructions
Are there any specific instructions or things that should be known prior to review?
Other information