refactor: performance, recording consistency, and quote logic fixes #1108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
rawpermission object was missing its reference point.2.Efficiency: The member role reduction logic was using an immutable spread pattern inside a reduce, leading to O(N^2) complexity.
isRecordingMessagestate, allowing users to still interact with the chat input while recording.toogleRecordingMessage) led to inconsistencies across hooks.Solution
permissionsRef.current.rawto ensure the early-exit logic works, preventing redundant state updates.roles.reducelogic for O(N) performance.Testing
npm run build).