Adding Trailing Comma in the Dart File.

[StrangeNoob]

Issue Description
As we are in refactor mode, Adding trailing commas will increase the readability of the code. It will help us auto-format the code and auto-comment the ending widget.

Before	After

Pros:

1. Makes the code more readable
2. With Bracket colorizer, figuring out the widget and all will be easy.
3. Helps to auto-format the code and auto-comment about the ending widget.

Cons:

1. As we have line restriction, It may be a problem as it increase the line. We can do something about this @Sagar2366, @palisadoes and @DeltaHarbinger.

Other Information
Instead of using print() to debug and view the output, the use of debugPrint() will be better than it won't show in the production.

Please ask mentors/maintainers to assign if you are willing to work on this issue.
I would to work on this but I have my exams starting tomorrow 😬. Let new member work on this.

[palisadoes]

Yes, this will increase the size of files, but the increase will be marginal in general. We need to stick with a limit. Let's see how the 300 line maximum works.

[palisadoes]

@StrangeNoob Can this be done automatically? That will help code consistency a lot. You are proposing a manual style change that may be difficult to enforce.

[StrangeNoob]

I don't have an idea about automating. @sumitra19jha can we tweak analysis_options, so it can help us? Otherwise, we can look some of the plugins that might help?

[sumitra19jha]

I don't think so.
Plus adding trailing comma and then sticking with 300 lines will be tough.

[StrangeNoob]

But with issue like #716 , #718 , #720 #721 may decrease the line of code significantly. Thats What I think.

[sumitra19jha]

Still, when creating a single file to handle the business logic of a particular page and organise the code, we would need:

1. Getter
2. Setter
3. Query Function
4. Mutation function
5. then Comments

This will take space

[StrangeNoob]

@sumitra19jha Sorry to disturb you, I came across part and part_of for splitting files. Look at this https://stackoverflow.com/questions/49594307/how-to-split-dart-class-in-flutter. It might help to write large code and split them in two files.

[sumitra19jha]

Hi @StrangeNoob,
I hope you are good and healthy. I am not at all disturbed.
To the best of my knowledge, when we are talking about restricting code to 300 lines, we are doing so to make the codebase more organized and structured. For example, we want to shift logic into one controller file, and widgets into another file. In the case of the controller, we further want to create a separate data model file. If the widget file is long we want to take a part of it, like the tile section and use it in another file. Now if more than one file needs that tile, then duplicate code can be avoided.

So as you can see, this work is organizing the codebase. Simply splitting the dart class into two files using extend would destroy this whole purpose of refactoring. I am not saying we cannot do it, I am just saying the reason in my opinion doesn't fit our purpose.

[nayakastha]

Hey @palisadoes. I have partially worked on this issue that is changing all the print statements into debugPrint for reducing the production junk in PR #744. It would be great if I could complete this issue. Can you assign it to me?

Also, I think Flutter's formatting tool inserts these commas automatically. And won't be much of a trouble to manually add them.

[palisadoes]

@nayakastha Done.