Shawn

The truth is, leaving teams in a state of technical debt because they can not properly specifiy a team-wide setting like line-length, is an order of magnitude more disruptive than...

Right, the "aliases" approach is basically how we deal with this now, so you would need to define a path value of: `["user", "user/", "user/:id"]` This request is basically asking...

The other problem this shows is how slow the baseline performance levels are. 22s for first-run, and 6 seconds for incremental, with a single library, feel at least 10x bigger...

This is really cool, I appreciate the lack of magic, and the highly readable code. It looks like it would be quite easy to support some special cases in auto-dispose...

> @esDotDev you can make it even simpler! > Sorry I don't use an IDE with a "refactor" button, what exactly would it do? I'm trying to limit the magic...

Totally, no need to get into the weeds on implementation details, other than to reveal use cases. In this case would be interesting to see how type checks would work...

Sorry I just meant null aware code from the perspective of generation, like: ``` "controller${field.canBeNull? "?" : ""}.dispose();", // Outputs controller.dispose() or controller?.dispose() ``` Similarly with type, the macro might...

> 2. Change the name in `main.dart`: > `WidgetCreator` still contains `MyButton1`, so you'd get an error in `main.dart` saying there is no `MyButton2`. You'd realize that's because you didn't...

Ah I see. Looking at how functional_widget works, you _can_ rename the `Foo` to `Bar` with IDE, and everything compiles fine. Once the code-generator runs again, it recreates the .g...

This approach is really hard to argue with because: 1. The important use cases in Flutter are small, and this addresses them all easily, and dart isn't really used outside...