Phaser Contributor Style Guide

[kevinthompson]

I'm curious if there's any sort of development style that contributors should adhere to when submitting examples or pull requests to the Phaser Github repository. I'd love to continue to help out, and I want my patches to be as easy to review and merge as possible.

 

 

[Mike]

I don't think that there is such a Guide, but just check phaser.js coding style and make yours look like it.

 

/**    * Returns a member at random from the group.    *    * @method Phaser.Group#getRandom    * @param {number} startIndex - Optional offset off the front of the array. Default value is 0, or the beginning of the array.    * @param {number} length - Optional restriction on the number of values you want to randomly select from.    * @return {Any} A random child of this Group.    */getRandom: function (startIndex, length) {}

Indents are tabs.. and pretty much that's what I see, but maybe Rich or someone for the team could make a short Guide for a convention.