Note, this is not a suggestion for a global strategy for TAB, just a healthy way that our feature team can create clean, linear Pull Requests that are very easy to code review.
Create branch with feature name
- hack code
- rebase off master
var Animal = function(classification, legs_count, size) { | |
this.classification = classification; | |
this.legs_count = legs_count; | |
this.size = size; | |
} | |
// An instance method; | |
Animal.prototype.description = function(){ |
# Bonus Bets - IMS, Wager Player, CRM Integration | |
Note: I am unsure of the exact difference between offers and Bonuses terminology. I'm also unsure that the 'Trigger Criteria' in Ian Hogg's spreadsheet means the same thing as a Trigger in IMS. | |
Reference: Ian Hogg's CRM Process List [here](https://tabcorp-digital.atlassian.net/ | |
wiki/x/QACqAg) | |
## Process | |
* 'Offers' will be entered into a CRM by Ian Hogg and Co. |
//container | |
const mapDispatchToProps=(dispatch)=>{ | |
return { | |
createComment: async (trackId, commentText, cb)=>{ | |
dispatch(createCommentAction(trackId, commentText)).then(cb); | |
} | |
} | |
} |