Hey, Christopher!

showOverpanel() is only able to render modules in an overpanel that are within the current extension - "Secondary" could only be opened by "Main" using showOverpanel().

If you want to bring the user to a different extension's overpanel module, you would use navigateTo(), and provide the specific extension name and module name.

Does that solution work for you?

Hey Jacob. This is rendering as standard text because of the value of your variant attribute. I recommend changing it to variant="standalone" if you'd like it to render as a styled element as opposed to standard text. Let me know if that solves the problem. Thanks!

Hey Bradley,

Currently the q2-checkbox component does not support custom icons to replace the checkbox. The design does offer different checkbox types ("favorite" or "toggle") as an alternative visual appearance, along with CSS override variables for theming, but we try to keep our component designs simple so that the different extensions utilizing them look and feel consistent.

Hey, Ethan!
Great questions. Thank you for all the description and code snippets, it really helps!

We do have a solution for you when it comes to creating a link in your modal:
There's a property in the showModal capability called customMarkup that you can use for the sentence containing your link. This will allow HTML to be displayed in the modal's message, so long as it's not a custom web component (we're working to support that soon). You can find details about customMarkup [her...

Hello!
Great question! This behavior is by design.

When a q2-input is in an error state and active, it will display an error message for the user. When it is in an error state, but not the active element, the error message disappears, and the red border and error icon remain to indicate an error.

For q2-calendar and q2-select, due to them both opening a popover when active, we did not include the error message because of the UI collisions it could cause. Instead, they only show t...