You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This looks really messy, but Form::Fields::Textarea exposes named blocks; HOWEVER,
5
+
we cannot conditionally render named blocks due to https://github.com/emberjs/rfcs/issues/735.
6
+
7
+
We *can* conditionally render components though, based on the blocks and argument combinations
8
+
users provide us. This is very brittle, but until https://github.com/emberjs/rfcs/issues/735
9
+
is resolved and a solution is found, this appears to be the only way to truly expose
10
+
conditional named blocks.
11
+
12
+
---
13
+
14
+
Regarding glint-expect-error
15
+
16
+
"@onChange" of the textarea only expects a string typed value, but field.setValue is generic,
17
+
accepting anything that DATA[KEY] could be. Similar case with "@value", but there casting to
18
+
a string is easy.
19
+
}}
1
20
<@form.Field @name={{@name}} as |field|>
2
-
<Form::Fields::Textarea
3
-
@label={{@label}}
4
-
@hint={{@hint}}
5
-
@error={{this.mapErrorsfield.rawErrors}}
6
-
@value={{this.assertStringfield.value}}
7
-
{{! The issue here is that onChange of textarea only expects a string typed value, but field.setValue is generic, accepting anything that DATA[KEY] could be. Similar case with @value, but there casting to a string is easy. }}
0 commit comments