Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a set of "canonical" lints for Google projects #326

Closed
wants to merge 2 commits into from

Conversation

matanlurey
Copy link
Contributor

This is based on internal discussions of what we enforce as part of the Google style guide, and what we would suggest going forward for all new Dart projects, specifically those created and owned by the Dart team (i.e. in dart-lang/*).

Please comment if you have suggestions about:

  • What the file name should be called and where it should live
  • The text used in google.md (make it more clear, etc)
  • Any obvious errors or omissions

If you disagree about this sets of lints, please contact me internally if you are a Dart team member or a Google employee - this is currently the set of lints we enforce internally + some additions that will be rolled out soon.

Community contributors, feel free to start a discussion if you feel strongly about something.

Awaiting LGTM from:

  • @bwilkerson for ownership of this package
  • @pq for Flutter and ownership of this package
  • @danrubel for Flutter and the structure of these type of "canonical" files
  • @srawlins for Google style guide/tooling enforcement
  • @kevmoo Dart PM

/cc @yjbanov

@zoechi
Copy link

zoechi commented Nov 7, 2016

See also #7, #251 (comment)

@matanlurey
Copy link
Contributor Author

Just an update. We are closing this and re-opening under another package.

@matanlurey matanlurey closed this Nov 12, 2016
@alexeieleusis
Copy link
Contributor

Can you please provide link to the new issue?

@matanlurey
Copy link
Contributor Author

This was replaced internally there is no new issue right now.

On Sat, Nov 12, 2016, 8:55 PM Alexei Eleusis Diaz Vera <
notifications@github.com> wrote:

Can you please provide link to the new issue?


You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
#326 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKQ7hxhx_XIZDgumsYRKlp70jIy-66wks5q9phGgaJpZM4KqqPJ
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants