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.
I kept finding myself needing more and more of the raw information from the Flowdock API. Instead adding those as attributes that get evaluated by the message_handler (and thus making things waaay more complicated) this seemed like the better approach.
Let's store the data (the hash for the incoming event) in the FlowdockMessage object. Then we can add methods to the message so that we can interrogate the message inside other addons.
This creates three useful methods:
FlowdockMessage#tags returns data['tags']
FlowdockMessage#thread_id returns data['thread_id']
FlowdockMessage#new_thread? returns data['id'] == data['thread']['initial_message']
If we wanted to add other methods we could do so easily.
Thoughts @bhouse