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
{{ message }}
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.
It would be nice to have a more generic clr-input-container.
So i can use third party controls within the clarity forms.
What is the change?
A generic form container element, to use with custom elements / controls.
Why should it go in Clarity?
Make it easy to use custom elements / controls that fit in the clarity form layout.
Would make clarity better compatible with third party controls.
This is an interesting request, and not something that is as simple as making a generic container. Each control also has to implement a set number of things to work properly with the container, and while I like the idea of opening this up so its more generic, its more complex than just a generic container.
I'll keep this as a feature request for the future, but for now you might consider reviewing how the input is implemented and seeing if you can duplicate the conditions in your own controls.
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed issues after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.
Summary
It would be nice to have a more generic
clr-input-container
.So i can use third party controls within the clarity forms.
What is the change?
A generic form container element, to use with custom elements / controls.
Why should it go in Clarity?
Make it easy to use custom elements / controls that fit in the clarity form layout.
Would make clarity better compatible with third party controls.
Examples
Workarounds
Currently i've created a very simple version in my project but it lacks the multiple layouts implementation and only works with a horizontal layout.
The text was updated successfully, but these errors were encountered: