It would be great if we stick to Kohana's Conventions and Coding Style: http://kohanaframework.org/3.2/guide/kohana/conventions
The reason the project slightly doesn't conform to all of Kohana's style and coding conventions is because we internally have different style and coding conventions that we follow, but we have tried to write the project as close them as possible for the community's sake.
Ok, no bracket's in separate lines. And always update the version date. What else? Otherways you're spending time to fix my code. :)
At the moment, here is a list of the style differences between Kohana and Leap:
$db = new Database();
$str = 'one' . $var . 'two';
Wow, that's almost opposite from Kohana's style! Well, I'll try to keep this in mind.
Here are a few other style differences between Kohana and Leap:
Changing && to AND and || to OR (Issues #3 and #49).
For this module, we have decided to change bullet point 5 (above) to read: