Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement trimming of leading/trailing whitespace and newlines for verification codes #586

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

kleysc
Copy link
Contributor

@kleysc kleysc commented Dec 19, 2024

Issue #585

Implementation Summary

Objective: Implement a hook to trim leading and trailing whitespace from verification codes, improving user input validation and enhancing the overall experience during setup.


Key Changes

  1. Custom Hook useTrimmedInputArray:

    • Created in ui/apps/router/src/hooks/custom/useTrimmedInput.tsx.
    • Manages multiple inputs, automatically removing spaces at the start and end of each entry.
  2. Updated Components:

    • VerifyGuardians.tsx: Integrated useTrimmedInputArray to sanitize the verification codes entered by guardians.

Features

  • Automatic trimming of whitespace during input or paste operations.
  • Enhanced user experience by reducing input validation errors.
  • Promotes cleaner and reusable code with the new custom hook.

Before and Now

  • Before: Input handling lacked automatic sanitization, leading to validation errors caused by whitespace.
  • Now: useTrimmedInputArray ensures all inputs are sanitized automatically, improving robustness and maintainability.

Summary by CodeRabbit

  • New Features

    • Introduced a new custom hook for managing trimmed input values.
    • Enhanced the VerifyGuardians component for improved input handling and verification of guardian hashes.
  • Bug Fixes

    • Streamlined logic for validating and pre-filling hashes.
  • Documentation

    • Updated exports to include the new custom hook for easier access in other components.

@kleysc kleysc requested review from a team as code owners December 19, 2024 00:06
Copy link

vercel bot commented Dec 19, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 3, 2025 10:13pm

Copy link
Contributor

coderabbitai bot commented Dec 19, 2024

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx

Oops! Something went wrong! :(

ESLint: 8.40.0

Error: Cannot read config file: /apps/router/.eslintrc.js
Error: Cannot find module '@fedimint/eslint-config'
Require stack:

  • /apps/router/.eslintrc.js
  • /node_modules/@eslint/eslintrc/dist/eslintrc.cjs
  • /node_modules/eslint/lib/cli-engine/cli-engine.js
  • /node_modules/eslint/lib/eslint/eslint.js
  • /node_modules/eslint/lib/eslint/index.js
  • /node_modules/eslint/lib/cli.js
  • /node_modules/eslint/bin/eslint.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
    at Module._load (node:internal/modules/cjs/loader:1074:27)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Module.require (node:internal/modules/cjs/loader:1339:12)
    at require (node:internal/modules/helpers:135:16)
    at Object. (/apps/router/.eslintrc.js:1:18)
    at Module._compile (node:internal/modules/cjs/loader:1546:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
    at Module.load (node:internal/modules/cjs/loader:1317:32)
📝 Walkthrough

Walkthrough

The pull request introduces a custom hook, useTrimmedInputArray, to manage trimmed input arrays within the VerifyGuardians component. This update enhances the handling of input states by initializing enteredHashes with an array of empty strings and streamlining the update process through the new hook. Additionally, the logic for validating hashes has been simplified, ensuring that the component maintains its functionality while improving input management.

Changes

File Change Summary
apps/router/src/hooks/custom/useTrimmedInput.tsx Added new useTrimmedInputArray hook for managing trimmed input arrays
apps/router/src/hooks/index.tsx Exported useTrimmedInputArray from custom hooks module
apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx Refactored input state management using useTrimmedInputArray hook and updated validation logic

Sequence Diagram

sequenceDiagram
    participant Component as VerifyGuardians
    participant Hook as useTrimmedInputArray
    participant State as Input State

    Component->>Hook: Initialize with empty values
    Hook-->>Component: Return values and handleChange
    Component->>Hook: Call handleChange with index and value
    Hook->>State: Update trimmed value at specific index
    State-->>Component: Reflect updated input state
Loading

The sequence diagram illustrates how the new useTrimmedInputArray hook manages input state, providing a clean and consistent way to handle input changes with automatic trimming.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (2)
apps/router/src/hooks/custom/useTrimmedInput.tsx (1)

3-3: Memoize cleanInput function

The cleanInput function should be memoized using useCallback to prevent unnecessary re-renders.

-const cleanInput = (value: string) => value.trim();
+const cleanInput = useCallback((value: string) => value.trim(), []);
apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx (1)

Line range hint 138-141: Memoize isAllValid check

The isAllValid check should be memoized to prevent unnecessary recalculations.

-const isAllValid =
-  peersWithHash &&
-  peersWithHash.every(({ hash }, idx) => hash === enteredHashes[idx]);
+const isAllValid = useMemo(
+  () =>
+    peersWithHash &&
+    peersWithHash.every(({ hash }, idx) => hash === enteredHashes[idx]),
+  [peersWithHash, enteredHashes]
+);
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf02442 and d0e882e.

📒 Files selected for processing (3)
  • apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx (5 hunks)
  • apps/router/src/hooks/custom/useTrimmedInput.tsx (1 hunks)
  • apps/router/src/hooks/index.tsx (1 hunks)
🔇 Additional comments (1)
apps/router/src/hooks/index.tsx (1)

6-6: LGTM! Verify the exported module exists.

The new export follows the established pattern and supports the PR's objective.

✅ Verification successful

The exported module exists at the expected location

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify that the exported module exists
fd --type f "useTrimmedInput.tsx" apps/router/src/hooks/custom

Length of output: 111

@kleysc kleysc changed the title Trim verification codes Implement trimming of leading/trailing whitespace and newlines for verification codes Dec 19, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx (2)

67-69: Optimize initial values array creation

The initial values array creation should be memoized to prevent unnecessary array allocations on each render.

-  const [enteredHashes, handleHashChange] = useTrimmedInputArray(
-    peersWithHash ? peersWithHash.map(() => '') : []
-  );
+  const initialValues = useMemo(
+    () => (peersWithHash ? peersWithHash.map(() => '') : []),
+    [peersWithHash]
+  );
+  const [enteredHashes, handleHashChange] = useTrimmedInputArray(initialValues);

229-229: Extract duplicated input handler

The same input handling logic is duplicated in two places. Consider extracting it to a memoized function.

+  const handleInputChange = useCallback(
+    (idx: number, value: string) => handleHashChange(idx, value),
+    [handleHashChange]
+  );
+
   // ... then use handleInputChange in both places:
-  onChange={(ev) => handleHashChange(idx, ev.currentTarget.value)}
+  onChange={(ev) => handleInputChange(idx, ev.currentTarget.value)}

Also applies to: 334-334

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06ca3a1 and 4b9766b.

📒 Files selected for processing (1)
  • apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx (5 hunks)
🔇 Additional comments (2)
apps/router/src/guardian-ui/components/setup/screens/verifyGuardians/VerifyGuardians.tsx (2)

106-116: LGTM: Error state clearing implemented

The implementation now properly clears the error state before prefilling hashes, addressing a previous review comment.


123-123: Optimize effect dependencies

Including handleHashChange in the dependency array could cause unnecessary re-renders.

@kleysc
Copy link
Contributor Author

kleysc commented Jan 3, 2025

The handleChange method has been simplified by removing index validation, as the provided indices are always valid in the context of use. This adjustment optimizes the code while maintaining its functionality.

Copy link
Member

@alexlwn123 alexlwn123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the contribution! Just a few comments to address before merging.

Comment on lines +8 to +14
const handleChange = (index: number, newValue: string) => {
setValues((prev) => {
const newValues = [...prev];
newValues[index] = cleanInput(newValue);
return newValues;
});
};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: wrap in useCallback

@@ -63,7 +64,9 @@ export const VerifyGuardians: React.FC<Props> = ({ next }) => {
const isHost = role === GuardianRole.Host;
const [myHash, setMyHash] = useState('');
const [peersWithHash, setPeersWithHash] = useState<PeerWithHash[]>();
const [enteredHashes, setEnteredHashes] = useState<string[]>([]);
const [enteredHashes, handleHashChange] = useTrimmedInputArray(
peersWithHash ? peersWithHash.map(() => '') : []
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you help me understand the purpose of the map? It looks like we're mapping the array entries to an empty string. Is this the intended behavior?

});
};

return [values, handleChange] as const;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: this return seems a bit strange ([] as const)

Once the returned items are memoized, you can just use return { values, handleChange }.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants