Jake Wharton
Jake Wharton
Other examples that keep coming up: - Stable ID - Accessibility (description, focus info) - Background color In order to support things like the pull-to-refresh case where on iOS it's...
Writing some things down that are in my brain so they're not lost as the weekend looms closer: If we intercept native UI nodes with these modifiers (for pull-to-request wrapping...
As far as I can tell, for protocol Redwood this will all be done in `ProtocolNode` which mostly has the same behavior as `WidgetNode` and also retains a parent reference....
I'm out until February. It was also not deemed something for stability sprint.
For things which only mutate an existing widget (e.g., background) it should be very quick. I expect within a week, barring any other distractions.
Mutating unscoped modifiers have landed. The test-app has been updated with a background color modifier that works on any node on any platform. Future work is allowing the generated callback...
I think the whole repository needs this
If you're doing the whole repo, I would consider only doing one type parameter at a time (such as all the ones which represent view type) in individual PRs. Otherwise...
And yes, any issue is fair game. If it doesn't have PR welcome it usually just means that it's larger in scope.
Actually we can probably infer kotlin-multiplatform from the role so perhaps it's just a single function or `var`.