UI DSL

[foresttoney]

Just to start out, I want to say that I am a huge Ory fan. I have been following the project for years and think what you are doing is awesome.

I have poked at Kratos several times over the years and every time I end up shelving it because it was either too early or too difficult to get set up (selfservice). The thing that I am wrestling with currently is the UI eDSL. I find it awkward. It isn't a fully dynamic and it isn't full static - but something in between.

For example, lets take a placeholder. There isn't a field to define this on in the identity schema. So, if you want a placeholder you have to hard code it somewhere in the front end. But, if I am hard coding validations in the front end, why am I going through gymnastics of trying to render a form against the UI DSL.

I might be missing something, but it feels like there should be a more idiomatic or straightforward way to implement this.

[aeneasr]

Appreciate the candidness, the UI DSL definitely needs overhaul but it probably won’t be started this year! Please use Ory Elements in the meanwhile for more convenient implementation:)

[foresttoney]

Is there any reason to not define the form statically and just ignore the UI DSL altogether? I mean, assuming of course that changes in the identity schema will also need to be also changed in the client.

[aeneasr]

It will probably work until it doesn't. The idea is that when you upgrade or add new features it keeps working, but that can't be guaranteed if you hard-wire your UI implementation. If you have sufficient test coverage, it's maybe (?) fine.

I think it's just better to use our SDKs and examples, you'll save yourself a lot of time: https://github.com/ory/elements

We're still working on the last mile for the SDKs but most of the things are already working.