Fixed computation of topic segments for MQTT DevFactory context #419
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.
The MQTT device factory adds topic segments to the mapping context, e.g.
foo/bar
givescontext.topic-0
set tofoo
.This was failing if the the topic was starting with a
/
, e.g./foo/bar
.This PR fixes the segmentation process, following the MQTT specification:
/foo
,foo
andfoo/
are different/
prefix,context.topic-0
is always an empty string/
suffix,context.topic-last
is always an empty stringfoo/bar
andfoo//bar
are equivalent, butfoo/bar
andfoo/ /bar
are different (andcontext.topic-1
will be a space character)