Luan Nico

Add the ability to provide a "hint text"

4

So while using this great library I thought it would be cool to be able to add a more in-depth description of the field. I thought with some bash hackery...

Current "covariance by default" paradigm is not respected by the compiler

5

After some digging around old issues, I can see there has been some discussion in the past about providing a more robust type system to Dart by including specific covariant/contravariant...

feat: allow bundle to take multiple inputs to take advantage of bash's wildcard

6

## Status **READY FOR REVIEW** ## Description Right now, if you provide more than one file for `mason bundle`, it will only look at the first file. That is because...

AnnotatedType support

7

New to Java 8, the AnnotatedType class carries annotations bind to types in Generic expressions. So if I write ``` @MaxLength(3) List myField; ``` I can get the `@NotNull` annotation...

This rule, when allowed, would force all Flutter colors to be uppercased (letters a-f should be replaced with letters A-F). This is similar to the rule: `use_full_hex_values_for_flutter_colors`. This would be...

# Description Deprecate `TapDetector` in favour of `TapCallbacks` ## Checklist - [x] I have followed the [Contributor Guide] when preparing my PR. - [x] I have updated/added tests for ALL...

Timer and TimerComponent APIs are inconsistent

4

Taking a look at Timer and TimerComponent, I realized they have a different nomenclature on their APIs: On [TimerComponent](https://github.com/flame-engine/flame/blob/main/packages/flame/lib/src/components/timer_component.dart#L20), the length/duration of the timer is called `period` and it is...

# What could be improved Currently only event updates that happen still within the component bounds are propagated. Even if a drag (or hover) started within the component, once the...

# What could be improved The different `*Callbacks` mixins should be configurable to allow for components to receive any events, regardless if they are "inside" the component or not; for...

# Problem to solve Would be useful to expose simplified ways to replace components within the component tree.  However it is not immediately obvious how these APIs would work...