Issue with Generators Input?

[hermygithub]

Hi All,

would there be an Issue with Generators Input for TextArea ?

When I grab the output from Select or Range Inputs via Generators.input() I do get the actual value of the input.

However, when I try to do the same on a TextArea Input, like ...

const textareaStrategySettingsImportInput = Inputs.textarea({ value: JSON.stringify( strategy_settings_export ), rows: 6, submit: false, });
const textareaStrategySettingsImport = Generators.input(textareaStrategySettingsImportInput);
console.log(rangeGain_7)
console.log(textareaStrategySettingsImport)

it gives me it's internals

Using it to display does give the actual value

<details>
  <summary>Strategy Settings</summary>
  ${ textareaStrategySettingsImportInput }
  ${ textareaStrategySettingsImport }
</details>

Any ideas on this ?
Is there a way to get the value of the TextArea Input in another way ?

Thx!

Herman

[Fil]

Try using two different fenced code blocks; the async generator is resolved between blocks (however, this is not specific to the textarea input, I'm struggling to understand why you'd see something different with other inputs if that's the only thing different).

[hermygithub]

OK, I see!

breaking it up in another fenced code block was indeed the solution! It seems I was too eager 😄

• first one is in the same code block
• second one is in another code block

Thx so much!

[hermygithub]

@Fil ,

quick follow-up question if I may 😄

Is there a way to set an input value programatically and have it propage through the code blocks ?

I'm trying to have some kind of 'import / export settings' functionality, so that I can read the input values, capture them in a JSON and set them on other given moments (via a button triggering a function)

When setting an input.value, I notice the visual change on the page, but it's value does not get propagated to the other code blocks.
I'm trying to wrap my head around Generators and Mutables, but it's not exactly the way I'd want it. Any ideas ?

Thx a lot!

Herman

[hermygithub]

Oops, sorry, I think I found it as it was mentioned https://observablehq.com/@observablehq/synchronized-inputs

the solution is to trigger the dispatchEvent() function after setting the input.value.

Cheers!