Shawn

If you like the idea, I can do a PR for you sometime this week.

We've created a lib here, if you'd like to include it in yours as a dependency that would be pretty cool :) https://pub.dev/packages/textstyle_extensions

Ya I had to basically embrace the shorthand since there were so many conflicts with the underlying API.

Ya that's fair, but we would end up with things like _textBaseline_ and _textDecoration_ and _textWordSpacing_. But ya I think you're right, that works a little better overall...

I've updated the API with better naming, thanks for the feedback.

Oh interesting, that would be better for performance, and also stop the fighting with the property names on TextStyle. I agree, much better :) The downside to this approach is...

Can't you just use textBuilder for this?

Just as one data point, I was looking to use `.select` to bind to some filtered lists on the model, where a new list does not necessarily indicate new data:...

That's interesting, my worry with this approach is just scalability though like it seems like I'll end up with tons of providers, and they will all (potentially) reference each-other and...

Ah I see, ya looking at it that way makes more sense... I need to maybe think of it as a model of providers, and not providing a single model.