feat(js-api): add FDS CX interfaces with `HTMLBuilder` naming convention

[markocikos]

References

• LPS-189354 Standardize renderer APIs

What is the goal of this PR?

In the PR, we are introducing the HTMLBuilder naming convention to public API:

• *Renderer is not quite right, as this is a property of a "Renderer" in DXP.
• *Component would not be right, as the function is not used as a React component. It's used as a plain old function.
• No suffix, like FDSFilter, might be confusing, as there are objects with the same name in DXP.
• We already introduced htmlBuilder as an argument of the ClientExtension component.

We are only adding API, and not renaming, so that the existing contracts don't break. After we migrate usages in DXP, we can delete old API here.

@bryceosterhaus @izaera What do you think?

[izaera]

What do you think?

:ok_hand:

[izaera]

Only thing that came to mind after writing the :ok_hand: ...

It's not really an HTMLBuilder but an HTMLElementBuilder. I don't think it matters so much because both concepts are equivalent but if we plan to have builders that return strings (as opposed to HTMLElements) in the future it can be worth reserving the name HTMLBuilder for stuff that returns strings and use HTMLElementBuilder for this. Maybe... 🤷

[bryceosterhaus]

I'm pretty flexible either way, but if I had to lean one way I would say go with HTMLElementBuilder since we are explicitly expecting it to return a single HTMLElement

[markocikos]

Good point! I'll push the change with rename.

[markocikos]

@bryceosterhaus Do we need to manually publish @liferay/js-api? Any special process to do this? Looking at versions, I guess it would be 0.4.0-pre.0.

[bryceosterhaus]

Yep we would need to manually publish, I can do so later this afternoon or tomorrow

[bryceosterhaus]

@markocikos https://github.com/liferay/liferay-frontend-projects/releases/tag/js-api%2Fv0.4.0-pre.0