[ANN] Quality Assistant: live code critics feedback

On Mar 27, 2015, at 5:14 AM, Yuriy Tymchuk <[hidden email]> wrote:

Dear Moose developers,

As you already know I am working on providing better code quality support in Pharo. You can use Code Critics in Pharo to detect bad practices and potential bugs. But launching the Critics Browser and running it on your code every now and then requires additional effort which demotivates many people in doing it.

I want to present you a compact tool called Quality Assistant
https://github.com/Uko/QualityAssistant#quality-assistant-𝑏𝑒𝑡𝑎-

It runs SmallLint rules on the code that you save and provides you with a critic feedback directly in the place where you code: the Nautilus Browser.

Quality Assistant is available for Pharo 4 from the Configuration browser. Please read about how to set it up here: https://github.com/Uko/QualityAssistant#set-up

I plan to introduce more features in the future and your feedback is much appreciated.

Cheers!
Uko
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Mar 27, 2015, at 10:46 AM, Yuriy Tymchuk <[hidden email]> wrote:

On 27 Mar 2015, at 14:37, Alexandre Bergel <[hidden email]> wrote:

Hi Yuriy!

Hi Alex!

Thanks for your tool! I will try to use it.

Thanks.

Just wondering, does it send data to a server? No pb with that, but I am wondering. If it does, it would be great that I can access what I actually send. Because maybe I have critics that I recurrently break.

Not at the moment. I will let everyone know if I’m collecting data and where it is available.

There is one I do not understand. Consider;

<Screen Shot 2015-03-27 at 10.37.10 AM.png>

What can I do to eliminate the guarding clauses. Which clauses by the way? Pretty obscure to me.

Ok, it looks that something is wrong with the rationale a bit. For this particular rule the point is that instead if having "ifTrue: [ … ]" at the end of a method, you can use "ifFalse: [ ^ self ]. …”.

Cheers!

Uko

Cheers,

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Mar 27, 2015, at 5:14 AM, Yuriy Tymchuk <[hidden email]> wrote:

Dear Moose developers,

As you already know I am working on providing better code quality support in Pharo. You can use Code Critics in Pharo to detect bad practices and potential bugs. But launching the Critics Browser and running it on your code every now and then requires additional effort which demotivates many people in doing it.

I want to present you a compact tool called Quality Assistant
https://github.com/Uko/QualityAssistant#quality-assistant-𝑏𝑒𝑡𝑎-

It runs SmallLint rules on the code that you save and provides you with a critic feedback directly in the place where you code: the Nautilus Browser.

Quality Assistant is available for Pharo 4 from the Configuration browser. Please read about how to set it up here: https://github.com/Uko/QualityAssistant#set-up

I plan to introduce more features in the future and your feedback is much appreciated.

Cheers!
Uko
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On 27 Mar 2015, at 14:50, Alexandre Bergel <[hidden email]> wrote:

Ah yes! 

Now I get it!

Thanks,

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Mar 27, 2015, at 10:46 AM, Yuriy Tymchuk <[hidden email]> wrote:

On 27 Mar 2015, at 14:37, Alexandre Bergel <[hidden email]> wrote:

Hi Yuriy!

Hi Alex!

Thanks for your tool! I will try to use it.

Thanks.

Just wondering, does it send data to a server? No pb with that, but I am wondering. If it does, it would be great that I can access what I actually send. Because maybe I have critics that I recurrently break.

Not at the moment. I will let everyone know if I’m collecting data and where it is available.

There is one I do not understand. Consider;

<Screen Shot 2015-03-27 at 10.37.10 AM.png>

What can I do to eliminate the guarding clauses. Which clauses by the way? Pretty obscure to me.

Ok, it looks that something is wrong with the rationale a bit. For this particular rule the point is that instead if having "ifTrue: [ … ]" at the end of a method, you can use "ifFalse: [ ^ self ]. …”.

Cheers!

Uko

Cheers,

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Mar 27, 2015, at 5:14 AM, Yuriy Tymchuk <[hidden email]> wrote:

Dear Moose developers,

As you already know I am working on providing better code quality support in Pharo. You can use Code Critics in Pharo to detect bad practices and potential bugs. But launching the Critics Browser and running it on your code every now and then requires additional effort which demotivates many people in doing it.

I want to present you a compact tool called Quality Assistant
https://github.com/Uko/QualityAssistant#quality-assistant-𝑏𝑒𝑡𝑎-

It runs SmallLint rules on the code that you save and provides you with a critic feedback directly in the place where you code: the Nautilus Browser.

Quality Assistant is available for Pharo 4 from the Configuration browser. Please read about how to set it up here: https://github.com/Uko/QualityAssistant#set-up

I plan to introduce more features in the future and your feedback is much appreciated.

Cheers!
Uko
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev