Is there a way to write `Modifier`s targeting specific `AttrsScope` subtypes, like `InputAttrsScope`...

# kobweb

[Norbi]

Is there a way to write `Modifier`s targeting specific AttrsScope subtypes, like InputAttrsScope ?
For example configuring TextInput() using `Modifier`s, like: TextInput(value = xyz, Modifier.onInput {...}.toAttrs()) ?

[David Herman]

Sadly this is a limitation of modifiers, and almost certainly the reason the JB APIs went with attrs blocks.

It is worth noting that you can to Modifier.a(...).b(...).toAttrs { ... } and the toAttrs block will be appropriately typed.

[David Herman]

The plan with Silk is to add a bunch of widgets that wrap the web and set the appropriate attributes for you

[David Herman]

In fact, Silk provides Input and TextInput widgets! So you can see how those work

[CLOVIS]

You will be able to do this when context receivers are added:

context(TextInputScope)
fun Modifier.b(…): Modifier { … }

[David Herman]

The problem is there is no scope

[David Herman]

I mean I might be missing something, which would be awesome

[David Herman]

but imagine the select web widget

[CLOVIS]

This is why AndroidX composables always introduce RowScope , ColumnScope , etc

[David Herman]

Select(Modifier.....)

[David Herman]

Those scopes ARE present in Kobweb too, but for the contents of the widget

[David Herman]

Select(...) {
  // this is SelectScope
}

[CLOVIS]

I may have misunderstood the original question then, because I believe that scope would satisfy the requirement for child modifiers

[David Herman]

Unless you can tag context onto regular parameters and not just methods / lambdas, I don't think there's a way to accomplish type-specific modifiers.

[CLOVIS]

Ah no the question was about AttrsInputScope subtypes, not sub-components. Sorry for the noise.

[David Herman]

No worries!