{"id":16477,"date":"2014-12-24T11:35:14","date_gmt":"2014-12-24T06:05:14","guid":{"rendered":"https:\/\/tothenewco.pro\/blog\/?p=16477"},"modified":"2014-12-24T11:35:14","modified_gmt":"2014-12-24T06:05:14","slug":"grails-stats","status":"publish","type":"post","link":"https:\/\/tothenewco.pro\/blog\/grails-stats\/","title":{"rendered":"Grails Stats"},"content":{"rendered":"

Here I am going to share one of the cool grails command that I discovered today i.e \u201cgrails stats\u201d. This command provides\u00a0basic statistics about the current grails application including\u00a0the number of files and lines of code.<\/p>\n

So, I tried this command in my grails project and see what I got.<\/p>\n

> grails stats
\n\"grails_stats\"<\/a><\/p>\n

Anybody looking at this stats can easily say :
\n1. Lot of code resides at controller layer.
\n2. Hardly any unit test case.
\nand so on..<\/p>\n

This result clearly depicts where I need to focus or improve upon. Next thing I need to do is refactoring. \ud83d\ude42<\/p>\n

Cheers!!<\/p>\n","protected":false},"excerpt":{"rendered":"

Here I am going to share one of the cool grails command that I discovered today i.e \u201cgrails stats\u201d. This command provides\u00a0basic statistics about the current grails application including\u00a0the number of files and lines of code. So, I tried this command in my grails project and see what I got. > grails stats Anybody looking […]<\/p>\n","protected":false},"author":113,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":7,"footnotes":""},"categories":[7],"tags":[1584,4840,1582,9,1583],"class_list":["post-16477","post","type-post","status-publish","format-standard","hentry","category-grails","tag-clean-code","tag-grails","tag-grails-stats","tag-groovy","tag-refactoring"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t