Hi @cerulean crater. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#TypeError: Cannot convert a Symbol value to a string
tawny riverBOT
Based on the information provided in the knowledge sources, I don't have specific details about nesting tables in @nextui-org/table or about the exact error you're encountering. However, the error message you're seeing - "TypeError: Cannot convert a Symbol value to a string" - is similar to an issue that has been reported in Next.js recently.
This error appears to be related to how Next.js handles certain prop types, especially in development mode. It's been reported as an issue in Next.js version 14.1.0 and is still present in the canary version 14.1.1-canary.50 Github Issue (https://github.com/vercel/next.js/issues/61966).
The error occurs when Next.js tries to warn about non-plain object prop binding. It seems to be caused by an issue in how React handles certain prop types, particularly when trying to serialize complex objects or functions.
While this doesn't directly answer your question about nesting tables in @nextui-org/table, it suggests that the error you're seeing might be related to how you're passing props to your table components, rather than an issue with the table nesting itself.
To troubleshoot this:
- Make sure you're using the latest stable version of Next.js and @nextui-org/table.
- Check if you're passing any complex objects or functions as props to your table components.
- If possible, try simplifying your table structure and gradually add complexity to identify where the error occurs.
If the problem persists, you might want to create a minimal reproducible example and report it to the @nextui-org/table repository, as it could be a specific issue with how their components interact with Next.js.