🐞 - TuiError produce an error with PolymorpheusComponent about taiga-ui

[waterplea]

We are currently working very hard to finish 4.0 so this won't be on our radar for a while. You can think on the fix in the meantime. I wonder if it's better to fix it in polymorpheus so it works everywhere. Current main in polymorpheus is the upcoming major release, fyi.

[waterplea]

Looks like the only way to fix it would be to wrap primitive values into objects, but that would be breaking change 🤔

[EricPoul]

It can be wrapped only for components and templates but if it didn't work before could it be considered as a breaking change?😄

[waterplea]

If we manage to do it only for components and templates — it won't be breaking :)

[EricPoul]

I see that it could be for component only since template examples works https://github.com/taiga-family/ng-polymorpheus/blob/main/projects/ng-polymorpheus/src/directives/outlet.ts#L65

[waterplea]

It would work but you won't be able to get value of the error since templates can only access keys of the context object:

<ng-template #tmp let-value="key">{{ value }}</ng-template>

[EricPoul]

Yep, so the goal is to try to wrap a primitive into the object for templates and components? It shouldn't be a breaking change for templates since it didn't work properly before(did work only if you hadn't reached a context). Is it a priority bug for you or should I consider making a PR?

[hakimio]

Why not just use @ngneat/error-tailor and avoid the tui-error boilerplate altogether?

[waterplea]

Moving it to ng-polymorpheus: taiga-family/ng-polymorpheus#449