SQLPage/examples/user-authentication/signin.sql

[Aesth]

In the example file, line 8:
case when $error is not null then 'We could not authenticate you. Please log in or [create an account](signup.sql).' end as error_message_md,
looks like a typo. The login component doesn't have an error_message_md property, but it does have a footer_md property. And on the component description page everything is correct.

[Aesth]

If both the footer and footer_md properties are specified, the footer_md property is not displayed. It is only displayed if the footer property is not specified. It's unclear why both are needed if one replaces the other.

Furthermore, the error_message and footer properties don't support links in the text.

[lovasoa]

It's unclear why both are needed if one replaces the other.

You are supposed to use one or the other. Use footer when the footer is plain text and footer_md when the footer contains rich text formatting, including links.

[Aesth]

Unfortunately, it's not clear from the documentation that they are interchangeable. Although it's still unclear why both exist. Wouldn't it be sufficient to have footer with the capabilities of the footer_md?

It seems that error_message_md from the example was intended to be similar to footer and footer_md, but was never implemented or was removed.

[lovasoa]

It's useful not to have to launch a markdown parser and html generator for every single piece of text. Additionally, one may want to use user-generated content in these fields, and not allow users to add their own links into the application.

[lovasoa]

error_message_md is implemented and works, it's just missing from the docs. Adding it right now, thanks for the warning !