-
The following error message pops up with this code and I can't find the bug:
Code 'use client'
import { useState } from 'react';
import * as Popover from '@radix-ui/react-popover';
import './styles.css';
import { FontAwesomeIcon } from '@fortawesome/react-fontawesome';
import { iconPopupSelector, iconCloseDialog } from 'roji-ui-icons';
import { H, IconButton, LinkButton } from 'roji-ui';
import { IdNameImageHref } from './IdNameImageHref';
import { RowWithLink } from './RowWithLink';
export interface MainSelectorPopupProps {
// currentItem: IdNameImageHref;
items: IdNameImageHref[];
headerLabel: string;
createLabel: string;
createUrl: string;
}
export const MainSelectorPopup = ({items, headerLabel, createLabel, createUrl }: MainSelectorPopupProps) => {
const [isOpen, setIsOpen] = useState<boolean>(false);
return (
<Popover.Root open={isOpen} onOpenChange={ setIsOpen}>
<Popover.Trigger asChild>
<IconButton>
<FontAwesomeIcon icon={iconPopupSelector} className="h-3 w-3"/>
</IconButton>
</Popover.Trigger>
<Popover.Portal>
<Popover.Content className="PopoverContent" sideOffset={5}>
<div style={{ display: 'flex', flexDirection: 'column', gap: 10 }}>
<H variant='mid' size="eyebrow">{headerLabel}</H>
<ul>
{items.map( (o) => {
return (<li key={o.id}>
<RowWithLink item={o} onClose={()=> setIsOpen(false)} />
</li>)
})}
</ul>
<LinkButton href={createUrl} onClick={()=> setIsOpen(false)} > {createLabel}</LinkButton>
</div>
<Popover.Close className="absolute right-[8px] top-[8px] h-5 w-5 items-center inline-flex text-foreground/80 hover:text-foreground cursor-pointer " aria-label="Close">
<FontAwesomeIcon icon={iconCloseDialog} className="h-4 w-4"/>
</Popover.Close>
<Popover.Arrow className="PopoverArrow" />
</Popover.Content>
</Popover.Portal>
</Popover.Root>
);
} |
Beta Was this translation helpful? Give feedback.
Answered by
mwawrusch
Feb 7, 2024
Replies: 1 comment
-
So this seems to have been fixed by the latest update of nextjs |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
benoitgrelard
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So this seems to have been fixed by the latest update of nextjs