Js4

Results 44 comments of Js4

> [#4590](https://github.com/heroui-inc/heroui/issues/4590) ? Good suggestion, could be related :) . But the hovering is no issue, It's probably hard to see in the video, but it's all interaction with the...

In my case I have around 20-30 rows and I have so much performance issues with it that I'm actually thinking of just using an styled native table instead. I...

@Drew-Chase I also got this if I used the table components outside of the table and not directly nested. I can share my implementation on Monday when I'm back at...

@Drew-Chase as I promised here is the implementation of my Table (note still WIP): ``` 'use client'; import { useMemo, useCallback, useState } from 'react'; import { Dropdown, DropdownTrigger, DropdownMenu,...

> Any updates? [@J4v4Scr1pt](https://github.com/J4v4Scr1pt) did you find the solution? > > Have same problem, even with 15 columns and 10 rows with simple text cells it becomes too slow and...

Does the action-id only change if you change the server-action code somehow? Or does it get a new Id on every build? Edit: Got the the [answer ](https://nextjs.org/blog/next-15#enhanced-security-for-server-actions) ![Image](https://github.com/user-attachments/assets/d52ea935-135f-4573-b377-e2b814ddfa90) I...

What a great work you have done investigating @LikeDreamwalker 🙌 You workaround seems solid, but should not be needed imo. This issue should be quite broad for people using Next...

> [@J4v4Scr1pt](https://github.com/J4v4Scr1pt) To reiterate what was mentioned above, you can essentially opt-out of this behavior when self-hosting → https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#overwriting-encryption-keys-advanced Thank you so much for your response! Sry that I missed...

Have you all tried the NEXT_SERVER_ACTIONS_ENCRYPTION_KEY? I still see this error from time to time, not as much as before but still. 🤔 Edit: Maybe I'm to eager, gonna let...

I think they can remove this completely instead and have it as it was in v14. The security should be up to us developers, you will not create an api-end-point...