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

fix: Default Bytes should only allow numbers #2380

Merged
merged 10 commits into from
Oct 30, 2024

Conversation

harshsbhat
Copy link
Contributor

@harshsbhat harshsbhat commented Oct 13, 2024

What does this PR do?

It makes sure that the user cannot type in "non number" characters for default bytes

Fixes #2359

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How should this be tested?

Test A:

Go to API settings -> enter a string as a default byte. It won't allow you to do so.

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Unkey Docs if changes were necessary

Summary by CodeRabbit

  • New Features

    • Enhanced the DefaultBytes component to accept only numeric input for better validation.
    • Added a description emphasizing that the default byte size must be between 8 and 255.
  • Bug Fixes

    • Updated input handling to ensure that the form state accurately reflects numeric values entered by the user.
  • Improvements

    • Reformatted query conditions in the OverridePage component for improved readability without altering functionality.

Copy link

changeset-bot bot commented Oct 13, 2024

⚠️ No Changeset found

Latest commit: 897cdad

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Oct 13, 2024

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

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 30, 2024 0:19am
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 30, 2024 0:19am

Copy link

vercel bot commented Oct 13, 2024

@harshsbhat is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Oct 13, 2024

📝 Walkthrough
📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in this pull request focus on the DefaultBytes component in the default-bytes.tsx file. The primary modification involves adding a type="number" attribute to the Input component within a FormField, ensuring that only numeric values can be entered. Additionally, the onChange handler has been updated to convert input values to numbers, aligning the input behavior with the validation requirements.

Changes

File Path Change Summary
apps/dashboard/app/(app)/apis/[apiId]/settings/default-bytes.tsx Added type="number" to Input component and updated onChange handler to convert input to number.
apps/dashboard/app/(app)/ratelimits/[namespaceId]/overrides/page.tsx Reformatted query conditions in db.query.ratelimitNamespaces.findFirst for improved readability.

Assessment against linked issues

Objective Addressed Explanation
Prevent non-numeric input in Default Bytes field (2359)

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 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

github-actions bot commented Oct 13, 2024

Thank you for following the naming conventions for pull request titles! 🙏

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

🧹 Outside diff range and nitpick comments (2)
apps/dashboard/app/(app)/apis/[apiId]/settings/default-bytes.tsx (2)

87-89: Excellent changes to restrict input to numbers only!

The modifications effectively address the issue of allowing only numeric input for the Default Bytes field:

  1. Adding type="number" to the Input component restricts user input to numbers only.
  2. Converting the input value to a number in the onChange handler ensures that the form state always contains a numeric value.

These changes align perfectly with the PR objectives and resolve the issue mentioned in #2359.

Consider adding a min and max attribute to the Input component to match the zod schema constraints:

 <Input
   className="max-w-sm"
   type="number"
+  min={8}
+  max={255}
   autoComplete="off"
   onChange={(e) => field.onChange(Number(e.target.value))}
 />

This will provide an additional layer of input validation directly in the browser.


Line range hint 52-57: Consider improving the error handling logic

The current implementation prevents submission when the defaultBytes value is unchanged or undefined. While this is a good check, it might be more user-friendly to handle this case differently.

Consider the following improvements:

  1. Move this check to the form validation level by extending the zod schema:
const formSchema = z.object({
  // ... other fields
  defaultBytes: z
    .number()
    .min(8, "Byte size needs to be at least 8")
    .max(255, "Byte size cannot exceed 255")
    .refine((val) => val !== keyAuth.defaultBytes, {
      message: "Please provide a different byte-size than the existing one",
    })
    .optional(),
});
  1. Remove the manual check in the onSubmit function:
 async function onSubmit(values: z.infer<typeof formSchema>) {
-  if (values.defaultBytes === keyAuth.defaultBytes || !values.defaultBytes) {
-    return toast.error(
-      "Please provide a different byte-size than already existing one as default",
-    );
-  }
   await setDefaultBytes.mutateAsync(values);
 }

These changes will provide more consistent error handling and improve the user experience by showing validation errors directly in the form.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7972170 and 1b86852.

📒 Files selected for processing (1)
  • apps/dashboard/app/(app)/apis/[apiId]/settings/default-bytes.tsx (1 hunks)
🧰 Additional context used
🔇 Additional comments (1)
apps/dashboard/app/(app)/apis/[apiId]/settings/default-bytes.tsx (1)

Line range hint 1-105: Summary of the review

The changes implemented in this PR effectively address the issue of allowing only numeric input for the Default Bytes field. The addition of type="number" and the conversion of input to a number in the onChange handler ensure that only valid numeric values are accepted and stored.

The overall implementation of the DefaultBytes component is solid, with proper form validation using zod and appropriate error handling. Two minor improvements were suggested:

  1. Adding min and max attributes to the Input component for additional browser-level validation.
  2. Refining the error handling logic for unchanged values by moving the check to the zod schema and simplifying the onSubmit function.

These suggestions aim to further enhance the user experience and maintain consistent validation throughout the component.

@harsha-kidambi
Copy link

/assign

Copy link

oss-gg bot commented Oct 13, 2024

The /assign command can only be used on issues, not on pull requests.

Copy link
Collaborator

@perkinsjr perkinsjr left a comment

Choose a reason for hiding this comment

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

see my last comment.

@harshsbhat
Copy link
Contributor Author

see my last comment.
give me 2 seconds. I will fix & push this

@harshsbhat
Copy link
Contributor Author

@perkinsjr using type="number" is going to keep that 0 at the start. Everything Is working fine now IMO. Please check

This will just make sure that onChange={(e) => field.onChange(Number(e.target.value.replace(/\D/g, "")))} the user cannot type a string AND not keep the 0 at the start too.

@perkinsjr perkinsjr merged commit 7c76890 into unkeyed:main Oct 30, 2024
20 of 24 checks passed
Copy link

oss-gg bot commented Oct 30, 2024

Awarding harshsbhat: 50 points 🕹️ Well done! Check out your new contribution on oss.gg/harshsbhat

@coderabbitai coderabbitai bot mentioned this pull request Dec 6, 2024
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default bytes allows characters while only needing numbers
3 participants