Hari07

Was this fixed? I tried to reproduce it by writing a title and text on a new page, then rebooted system and when I came back nothing was changed

Is it possible it's a windows 11 thing? Cos I'm on 10, but not really sure if something like this could be OS related

That kind of problem exists for most widgets, exposing the paint would allow for a lot more customisation, but afaik every widget takes in a whole lot of parameters like...

So should I change the default to be `StrokeCap.butt` instead of `StrokeCap.square`

That certainly does seem easier, but what if you want a circular ended determinate progress indicator IMO it's a flaw in the design if the type of the end determines...

It'd be great if someone on the team could elaborate what the failed tests show, from what I can see there's no information about why those test failed

It seems like the tests failed to compile, not sure about why but doesnt look related to this PR, would be great if someone could suggest how this can be...

We had made a solution for this exact use-case, just pulled it into an open source package https://github.com/sodality-tech/graphql-cache-inspector https://pub.dev/packages/graphql_cache_inspector

> You are likely seeing this problem because you just imported `package:widgetbook_annotation` but did not import `package:widgetbook`. > > The extension method which makes `knobs` available from `context` is defined...

I was able to do that too, but if not for knobs widgetbook doesn't need to be a dependency, dev dependency is enough