-
Notifications
You must be signed in to change notification settings - Fork 199
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
[wct] Moving from clang + tslint to gts #224
Comments
Closed
justinfagnani
pushed a commit
that referenced
this issue
Jul 10, 2018
…verter (#224) * Refactor BaseConverter into UrlHandler, ProjectConverter * fix the includes comment to explain the complexity of it * respond to @usergenic PR feedback * fix basePackageName unsafe reference * comment on shadycss handling logic * fix lazy endswith() matching * remove bad url check * npm run format * regex too broad, lets get specific * respond to justin feedback
7 tasks
Closing due to inactivity. |
This was referenced Sep 15, 2021
This was referenced Nov 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Google has a nice tool which combines capabilities of tslint and clang fromat in one tool: https://github.com/google/ts-style
The issue with the current configuration is that clang and tslint rules are conflicting. Originally I wanted to tweak tslint configuration, but in the end I think moving to gts is a better idea.
Is that ok with you guys if I make a PR for this?
The text was updated successfully, but these errors were encountered: