Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update TSLint rules #503

Open
jak-atx opened this issue May 25, 2018 · 0 comments
Open

Update TSLint rules #503

jak-atx opened this issue May 25, 2018 · 0 comments
Assignees
Labels
component/infrastructure Infrastructure related to building and testing component/plugin/h5c The plugin for the vSphere HTML5 client kind/task Work not related to changing the functionality of the product severity/3-moderate Medium usability or functional impact. Potentially has an inconvenient workaround.

Comments

@jak-atx
Copy link
Contributor

jak-atx commented May 25, 2018

As recommended by security team vic-ui TSLint config should be updated by adding the rulesets from the following Microsoft contribution:
https://github.com/Microsoft/tslint-microsoft-contrib

@jak-atx jak-atx added component/plugin/h5c The plugin for the vSphere HTML5 client status/needs-estimation The issue needs to be estimated by the team labels May 25, 2018
@lmalvins lmalvins self-assigned this Jun 8, 2018
@zjs zjs added severity/3-moderate Medium usability or functional impact. Potentially has an inconvenient workaround. component/infrastructure Infrastructure related to building and testing kind/task Work not related to changing the functionality of the product and removed status/needs-estimation The issue needs to be estimated by the team labels Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/infrastructure Infrastructure related to building and testing component/plugin/h5c The plugin for the vSphere HTML5 client kind/task Work not related to changing the functionality of the product severity/3-moderate Medium usability or functional impact. Potentially has an inconvenient workaround.
Projects
None yet
Development

No branches or pull requests

3 participants