B. Camphart

Additional notes: - If the supplied SpanStyle has no actual properties, the issue does not happen. - Using italics instead of bold also causes the problem.

Additionally, this applies to the BasicText component too. If you run the following test: ``` @Composable fun TextFieldTest() { val value = AnnotatedString( "abcd", spanStyles = listOf( AnnotatedString.Range(SpanStyle(fontWeight = FontWeight.Bold),...

to @mcpiroman's point, maybe the syntax can put the context in the next line, similar to the existing `where` syntax: ```kotlin fun List.sum(): T context(Monoid) { } ``` It would...

That's already accomplished with the `ignoredScenes` property, though, isn't it? If the idiomatic thing is to have the files, and it's just about ignoring those during compilation, then does a...

I see, that makes sense. Probably related to #169 then?

Can this be solved by embedding a note that you want referenced into a "scene"?

I know exactly what you're talking about, but that can be changed through your theme or custom css snippets.

I've been thinking about this, and I want to get your opinion @kevboh 1. every scene file has a longform property that says if it should be included in compile....

I think that makes sense. How do you feel about the written property name being customizable, but defaulting to `longfrom-order`?

@kevboh I think this one should have been closed with #194