FLEX: flex_groupmessage moved into for, as it seems that it needs to be determined per page #223
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 FLEX_NEXT decoder was showing more messages than the FLEX decoder. This change in the FLEX decoder makes them visible.
Previously the field
flex_groupmessage
was was used for all pages. If the first page set the flag, subsequent pages would falsely process the data as a a group message.I'm not sure if this change is correct but for all cases.
This might partially fix the following issues:
Full output with verbose 3 with this change:
FLEX:
FLEX_NEXT: