<commit_before><commit_msg>code style guide<commit_after># code style guide for the tiles web client



-		follow AngularJS formatting guidelines and best practices

(http://google-styleguide.googlecode.com/svn/trunk/angularjs-google-style.html)
(https://github.com/johnpapa/angularjs-styleguide)


-		use the tls- directive prefix for custom 'tiles' directives


-		always format HTML, JavaScript and JSON according to standards

(https://google-styleguide.googlecode.com/svn/trunk/htmlcssguide.xml)
(https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml)
(https://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml)


-		prefer single quotes in script where possible


-		always indent with 2 spaces (soft-tabs)


-		avoid unnecessary white space or line breaks


-		avoid code lint by any code management tool


-		use camelCase for scripting


-		use snake-case for mark-up, style names, file and folder names


-		use lower/case for URLs


-		write literate code with meaningful property, method or element names


-		avoid using abbreviations at all times!       


-		use file naming conventions consistent with code they implement


-		add meaningful comments when merging or pushing code







{'fraction_non_alphanumeric': 0.0762987012987013, 'fraction_numerical': 0.0008116883116883117, 'mean_word_length': 3.81640625, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 3}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5960325', 'n_tokens_mistral': 402, 'n_tokens_neox': 368, 'n_words': 120}