The Tweets You Missed in August
Here are the tweets you likely missed last month!
SonarQube 6.5: read the news and see in it screenshots! https://t.co/jHvv1Ts0v0https://t.co/nTWDOyafg5 pic.twitter.com/pO3FLNp4Wp
— SonarQube (@SonarQube) August 23, 2017
SonarTS 1.0 is out: state of the art code analyzer for @typescriptlang #opensource https://t.co/2mVnJ0d7Lz pic.twitter.com/EEmaUgXMnm
— SonarQube (@SonarQube) August 28, 2017
SonarTSQL 1.0 is out: first version of the code analyzer for Transact-SQL languagehttps://t.co/cC6KEWz3iE pic.twitter.com/aqkN5atEdB
— SonarQube (@SonarQube) August 29, 2017
The upcoming SonarTSQL code analyzer in action to detect conditional structure with same implementation in all branches #teaser pic.twitter.com/QuhdMwLt8n
— SonarQube (@SonarQube) August 9, 2017
SonarLint for Visual Studio 3.4 adds the support of C and C++ https://t.co/IQqctMVlN6 pic.twitter.com/5aHtvBJ0gN
— SonarLint (@SonarLint) August 23, 2017
SonarCFamily 4.11 Released: 2 new rules and even more useful issue reporting in case of dataflow analysis. https://t.co/kiWS38A3rI pic.twitter.com/WKsyy0XirW
— SonarQube (@SonarQube) August 4, 2017
SonarJava 4.12 provides 13 new rules to spot Bugs or Code Smells relating to #stream #lambda #java8 and more .... https://t.co/WayagtQ0GD pic.twitter.com/6J3wAXgP3l
— SonarQube (@SonarQube) August 2, 2017
Pattern matching in action with SonarJava to detect unconditional jump statements in loops #bugs pic.twitter.com/0RBuwofOfa
— SonarQube (@SonarQube) August 3, 2017
SonarC# 6.2 Released: 20 new rules. Example with "Method parameters should be declared with base types" https://t.co/bylL8qDlv3 #csharp pic.twitter.com/vri88h2IVn
— SonarQube (@SonarQube) August 3, 2017
Example of bug raised by SonarC# when calling a non-side-effect function without using the return value #csharp pic.twitter.com/cr5W1qiEm5
— SonarQube (@SonarQube) August 3, 2017
Another example of a code smell reported on @roslyn. Spotted by rule "Boolean expressions should not be gratuitous"https://t.co/pUX23VdQGz pic.twitter.com/NdkJetif7T
— SonarQube (@SonarQube) August 9, 2017
Bunch of highly suspicious unconditional return statements in loops reported on @roslynhttps://t.co/6GBFi9xMUD pic.twitter.com/d6ghf3Lg2J
— SonarQube (@SonarQube) August 10, 2017
Bug detection rule "Return values from functions without side effects should not be ignored" in action on C# code pic.twitter.com/YNaaOe2hV4
— SonarQube (@SonarQube) August 29, 2017
SonarC# 6.3 Released: 4 new rules available #csharp https://t.co/7kNKFRc2a7 pic.twitter.com/OzFo837nxe
— SonarQube (@SonarQube) August 30, 2017