Is there a practical way to apply rate-limiting on the number of phx-changes before cutting off a liveview?

Hi,

Just started with LiveView and found it very promising indeed, especially for someone like me with limited front-end javascript/ajax knowledge.

My question is there a practical way to apply rate-limiting on the number of phx-changes before cutting off a liveview, in case a form is misused for example? Would it mean keeping a count of each phx-change per phx-session separately, or is there a better way?

1 Like