Lucas Oliveira

Hey @jezell, thank you for your contribution. Could you send us a use case explaining a real scenario? What would you like to do with this new property?

@lrhn I believe your suggestion of create those two lint rules `handle_exceptions` and `document_exceptions` are a good start to ensure that developers are documenting their code better

@lrhn what if we create something like `@Deprecate`? The comment could be set automatically. ```dart @Throws(AnyException) int parseIntStrict(String input) { if (!RegExp(r'^\d+$').hasMatch(input)) { throw FormatException("Invalid number format"); } return int.parse(input);...

Thank you for your contribution. Currently, we are handling the `onTapUp`. The Mix would provide a way to handle other behaviors, such as `onTapDown`. if we create `onPressedDown` and `onPressedUp`...

@leoafarias Besides moving, we should merge them into only one file. because of this, we will have one file on the left side and the user can navigate between the...

The same is happening with factory methods and methods. ```dart class A { A(); factory A.foo(A v) => A(); A foo(A v) => this; } void bar(A value) => print(value);...