Reorder constructors and fields in code example on Effective Dart: Usage page

[Turskyi]

Page URL

https://dart.dev/effective-dart/usage.html

Page source

https://github.com/dart-lang/site-www/tree/main/src/effective-dart/usage.md

Describe the problem

The examples on the ‘Effective Dart: Usage’ page (https://dart.dev/effective-dart/usage) currently place fields before constructors. This is inconsistent with the Dart and Flutter style guides, which recommend placing constructors first in a class. This inconsistency could potentially lead to confusion for developers, especially those who frequently switch between Dart and Flutter projects.

Expected fix

Reorder the constructors in all examples on the ‘Effective Dart: Usage’ page to align with the Dart and Flutter style guides. Specifically, adhere to the guidelines from ‘sort_constructors_first’ (https://dart.dev/tools/linter-rules/sort_constructors_first).

Additional context

This issue was raised following a pull request (#5452) that aimed to align the examples with the official style guides. The discussion in the pull request highlighted the tradition of placing fields before constructors in Dart, which is more familiar to developers from other programming languages. However, given the close relationship between Dart and Flutter, it’s worth considering the impact of these stylistic differences on the developer experience. This issue aims to gather feedback from the community on this matter.

I would like to fix this problem.

• I will try and fix this problem on dart.dev.

[atsansone]

Per comments in #5462 , closing this issue as Won't fix.

[Turskyi]

Hello @atsansone,

I've noticed that the issue regarding the ordering of constructors and fields in the Dart style guide was closed with a reference to a previous discussion in issue #5462. I understand that decisions on such matters are complex and involve the consideration of various factors, including community standards and historical precedents.

However, I feel that the closure of the issue without an extensive community discussion may have preempted a valuable opportunity for collective input. The Dart and Flutter communities are vibrant and diverse, with a wide range of experiences and perspectives that could contribute to a more informed decision on coding style practices.

Given the significance of this topic and its potential impact on the developer experience, I believe it would be beneficial for the community to have a more open forum for discussion. This would ensure that any decision made reflects a consensus or at least a majority viewpoint, rather than the perspective of a single individual or a small group.

I respectfully request that we reconsider the closure of this issue and allow for a period of open commentary, inviting the community to share their thoughts and experiences. This could help us reach a more democratic and inclusive resolution that aligns with the best interests of both Dart and Flutter developers.

Thank you for your time and understanding.