Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should not store chat state messages, which contain a thread element. #513

Merged
merged 1 commit into from
Jan 18, 2016

Conversation

sco0ter
Copy link
Contributor

@sco0ter sco0ter commented Jan 14, 2016

The problem was, that the logic stored empty chat messages, which contained a thread and chat state. The loop first checked the namespace of the thread, which was empty and therefore thought it should store it.

The problem was, that the logic stored empty chat messages, which contained a thread and chat state. The loop first checked the namespace of the thread, which was empty and therefore thought it should store it.
@guusdk
Copy link
Member

guusdk commented Jan 15, 2016

+1

Should his go in 4.0.1?

@sco0ter
Copy link
Contributor Author

sco0ter commented Jan 15, 2016

sure, why not.

guusdk added a commit that referenced this pull request Jan 18, 2016
Should not store chat state messages, which contain a thread element.
@guusdk guusdk merged commit fa5b0ee into igniterealtime:master Jan 18, 2016
@guusdk
Copy link
Member

guusdk commented Jan 18, 2016

I've created https://igniterealtime.org/issues/browse/OF-1048 to track this change in the changelogs (which we generate from JIRA).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants