27 Mar
2015
27 Mar
'15
10:03 a.m.
Hi Stephan,
this is still work in progress solution, but the idea behind it is that you define the
packages that you are developing, and they are checked in each image that you open.
Example use case: when I develop Quality Assistant and use a fresh image every day I donβt
want to re-setup that I want to check it. If you have other workflows in mind please let
me know.
Uko
On 27 Mar 2015, at 09:47, stephan
<stephan(a)stack.nl> wrote:
Hi Uko,
Looking nice! Why is the package names regex a global for all future images?
Stephan
On 27-03-15 09:14, Yuriy Tymchuk 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
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev