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
As far as I can tell, it isn't possible to specify the of type of lists in computed fields the way that you can in non-computed fields. Thus, this is possible:
Instead, you can only specify an untyped list, and in the generated output you end up with this:
segments: list
But this raw list type isn't defined!
There may be reasons to explicitly disallow typed lists in computed fields, and if so I'd be curious why! Otherwise, this feels like an oversight to me.
The text was updated successfully, but these errors were encountered:
I agree there are definitely some gaps in regards to which types can be used for computed fields. This will be addressed before 1.0 is released. (Also see #149)
As far as I can tell, it isn't possible to specify the
of
type of lists in computed fields the way that you can in non-computed fields. Thus, this is possible:But this is not:
Instead, you can only specify an untyped list, and in the generated output you end up with this:
segments: list
But this raw
list
type isn't defined!There may be reasons to explicitly disallow typed lists in computed fields, and if so I'd be curious why! Otherwise, this feels like an oversight to me.
The text was updated successfully, but these errors were encountered: