refactor(desktop): add mqtt properties component #1817
Merged
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?
Please describe the current behavior and link to a relevant issue.
Issue Number
Example: #123
What is the new behavior?
This pull request includes changes to refactor the handling of MQTT properties in the
MsgLeftItem
andMsgRightItem
components by creating a newMqttProperties
component. The most important changes include the creation of the new component and the replacement of the existing property handling code in theMsgLeftItem
andMsgRightItem
components.Creation of
MqttProperties
component:src/components/MqttProperties.vue
: Added a new component to handle the display of MQTT properties, including theKeyValueEditor
for user properties.Refactoring of
MsgLeftItem
andMsgRightItem
components:src/components/MsgLeftItem.vue
: Replaced the inline property handling code with the newMqttProperties
component and removed the import ofKeyValueEditor
. [1] [2]src/components/MsgRightItem.vue
: Replaced the inline property handling code with the newMqttProperties
component and removed the import ofKeyValueEditor
. [1] [2]Please describe the new behavior or provide screenshots.
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