What are you trying to do?
I have a component that is called SelectCountry for website country selection, this has a Select component from the basic plasmic components inside.
The SelectCountry is present both in the header and on the footer of the website.
This worked before but broke with something, the one on the header works just fine, the one on the footer does not.
What are the reproduction steps?
This is replicable creating a fresh nextjs plasmic project starting from the project below
Thanks for providing the steps. I’m able to reproduce that. It seems like the select dropdown is not showing up because it doesn’t have enough space below it. Ideally, it should show the popup above the Select trigger when there is not enough space below it.
We will investigate further and fix it accordingly.
Because the Plume components are deprecated, we recommend, switching to the newer, Customizable Select component instead. That should resolve the issue.
Thanks @muhammad_asim, this works but I’m getting another error.
Works fine when creating a new project from the above plasmic id, but not when replacing the component in the existing project. The wrapper component itself is not providing any prop to the select component as on the fresh one but I’m getting the following error.
Hello, just an update. Today when I try to create a new component using the Select as a base on the same project it fails to create the component. Idk if the error in console is related
4506.c3a201e1.js:465 Error evaluating custom code `(
$props.showDescription
)`: ReferenceError: $props is not defined
at Object.get (index.1e5028e9.js:2:4979939)
at Object.eval (eval at <anonymous> (index.1e5028e9.js:2:4979433), <anonymous>:5:11)
the issue was on me, I was renaming the first attempt and when I was creating a new one it was bringing me to the old one (select wrapper component)
I was able to migrate two of our selects to the new components, seems the “Replace all instances” function won’t work as slot contents and variants are different
Seems to work fine on the final build but I’m getting an error during development, I managed to trace this error and it disappears when I remove a useContext call to a StoreCheckoutContext, I’ve tried replacing the StoreCheckoutProvider contents with a null value but still happens, seems unrelated to me.