-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #462 from hivemq/feature/deprecate-bad-subscribe-o…
…ptions Deprecate bad subscription options and add replacements
- Loading branch information
Showing
8 changed files
with
597 additions
and
33 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
| Option | Long Version | Explanation | Default | | ||
|--------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| | ||
| `-t` | `--topic` | The MQTT topic the client will subscribe to. | | | ||
| `-q` | `--qos` | Define the quality of service level. If only one QoS is specified it will be used for all topics.<br> You can define a specific QoS level for every topic. The corresponding QoS levels will be matched in order to the given topics. | `0` | | ||
| `-of` | `--outputToFile` | Append the received publish messages to a file. Creates the file if it does not exist. | | | ||
| `-b64` | `--base64` | Whether the received publish messages will be base64 encoded. | `false` | | ||
| `-J` | `--jsonOutput` | Print the received publishes in pretty JSON format. | `false` | | ||
| `-T` | `--showTopics` | Prepend the specific topic name to the received publish. | `false` | | ||
| `-up` | `--userProperty` | A user property of the subscribe message. | | | ||
| Option | Long Version | Explanation | Default | | ||
|--------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| | ||
| `-t` | `--topic` | The MQTT topic the client will subscribe to. | | | ||
| `-q` | `--qos` | Define the quality of service level. If only one QoS is specified it will be used for all topics.<br> You can define a specific QoS level for every topic. The corresponding QoS levels will be matched in order to the given topics. | `0` | | ||
| | `--output-to-file` | Append the received publish messages to a file. Creates the file if it does not exist. | | | ||
| | `--base64` | Whether the received publish messages will be base64 encoded. | `false` | | ||
| `-J` | `--json-output` | Print the received publishes in pretty JSON format. | `false` | | ||
| `-T` | `--show-topics` | Prepend the specific topic name to the received publish. | `false` | | ||
| | `--user-property` | A user property of the subscribe message. | | |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.