[Hawkular-dev] UI Development changes

NOTE: these changes are only relevant to UI development in typescript. To follow on to previous messages about the upcoming tslint UI changes. Last time, we discussed upcoming changes (more strict coding standards) to TS development and I sent out the tslint.json file for discussion. That has been implemented now that we have released, and should provide a more consistent development style for all. In addition, the tslint rules will steer away from known typescript issues and allow third party contributions without a ton of PR turnaround (since much of it is automated and can be done at the client machine). Additional rules will be added as we mature our codebase. If you feel the rules are too strict and need to subvert “The Man”, feel free to do so with: /* tslint:disable:no-unused-variable */. The rulewill tell you which rule it failed on so its easy to add this clause. The disable rule takes effect until the end of the file or a corresponding tslint:enable command is given. So if you have done previous UI dev work, expect additional linting rules to fire now. There are now both white-space formatting and syntax rules that are required. While you are free to use any tools to develop, Pro Tip: Install (https://github.com/vvakame/typescript-formatter <https://github.com/vvakame/typescript-formatter>) via: npm install -g typescript-formatter and then you can use at any time: tsfmt -r to recursively format all the whitespace in the files according the the tslint.json rules established (this should be run from the ’scripts’ directory). — Mike