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

docs: Fixes a few typos in the docs from revoke to modify / retrieve #2212

Merged
merged 2 commits into from
Oct 5, 2024

Conversation

harshsbhat
Copy link
Contributor

@harshsbhat harshsbhat commented Oct 5, 2024

What does this PR do?

Fixes a few typos in the docs

Fixes #2211

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps use understand why this PR exists

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
  • Test B

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

  • Documentation
    • Updated the update_key function documentation to clarify its purpose and parameter changes.
    • Revised the update_remaining function documentation to reflect modifications in parameter descriptions.
    • Enhanced the Get API key functionality documentation to specify the correct use of the keyId parameter for retrieval instead of revocation.

Copy link

changeset-bot bot commented Oct 5, 2024

⚠️ No Changeset found

Latest commit: baaa07f

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 5, 2024

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

Name Status Preview Comments Updated (UTC)
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 5, 2024 3:08pm

Copy link
Contributor

coderabbitai bot commented Oct 5, 2024

📝 Walkthrough

Walkthrough

The pull request includes updates to the documentation for three functions: update_key, update_remaining, and the "Get" API key functionality. Key changes involve renaming the key_id parameter to keyId, clarifying the intent of this parameter from revocation to modification or retrieval, and updating the function specifications to indicate their return types. These modifications aim to enhance clarity regarding the functionality and usage of the respective functions.

Changes

File Path Change Summary
apps/docs/libraries/ex/functions/update_key.mdx Updated documentation for update_key function, renamed key_id to keyId, clarified purpose and parameter descriptions.
apps/docs/libraries/ex/functions/update_remaining.mdx Updated documentation for update_remaining function, modified keyId description, added return type specification.
apps/docs/libraries/ts/sdk/keys/get.mdx Updated documentation for "Get" API, changed keyId description from revocation to retrieval.

Assessment against linked issues

Objective Addressed Explanation
Correct the description for keyId in the SDK for get operation (#2211)

Possibly related PRs

Suggested reviewers

  • mcstepp
  • chronark
  • perkinsjr

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

vercel bot commented Oct 5, 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

github-actions bot commented Oct 5, 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 (4)
apps/docs/libraries/ex/functions/update_key.mdx (3)

18-18: Approved change with a minor suggestion

The update from "revoke" to "modify" accurately reflects the function's purpose and aligns with the PR objectives. This change improves the documentation's clarity.

For consistency with the function's title and description, consider changing "modify" to "update":

- The ID of the key you want to modify.
+ The ID of the key you want to update.

This minor adjustment would maintain consistency throughout the documentation.


Line range hint 7-7: Inconsistency in parameter naming

There's an inconsistency between the method signature and the request section regarding the key identifier parameter:

  1. The method signature uses key_id:

    @spec update_key(binary(), map()) :: :ok
  2. The request section uses keyId:

    <ParamField path="keyId" type="string" required>

For consistency and to avoid confusion, consider using the same naming convention throughout the documentation. Given that the request section uses camelCase, updating the method signature might be appropriate:

- @spec update_key(binary(), map()) :: :ok
+ @spec update_key(binary(), map()) :: :ok
# Example usage in the code snippet
UnkeyElixirSdk.update_key("key_cm9vdCBvZiBnb29kXa", %{
  # ... other parameters ...
})

This change would ensure consistency across the documentation and code examples.

Also applies to: 18-18


Line range hint 61-65: Incorrect description for the remaining parameter

The description for the remaining parameter appears to be incorrect. It's currently identical to the description for the expires parameter:

<ParamField body="remaining" type="int | nil">
  Update the expire time of a key.

The expire time is a unix timestamp in milliseconds.
</ParamField>

This seems to be a copy-paste error. The remaining parameter likely refers to the number of uses remaining for the key, not its expiration time. Consider updating the description to accurately reflect the purpose of the remaining parameter:

<ParamField body="remaining" type="int | nil">
-  Update the expire time of a key.
-
-The expire time is a unix timestamp in milliseconds.
+  Update the number of remaining uses for the key.
+
+  Set to `nil` to remove the limit on remaining uses.
</ParamField>

Please verify the correct meaning of the remaining parameter and update the description accordingly.

apps/docs/libraries/ts/sdk/keys/get.mdx (1)

Line range hint 1-138: Consider adding testing information to the documentation

The documentation for the "Get" operation is now accurate and consistent. To further improve its completeness, consider adding information on how to test this functionality. This aligns with the PR checklist item "How to test" which is currently unfilled.

Would you like assistance in drafting a "How to test" section for this documentation?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 2288ebf and baaa07f.

📒 Files selected for processing (3)
  • apps/docs/libraries/ex/functions/update_key.mdx (1 hunks)
  • apps/docs/libraries/ex/functions/update_remaining.mdx (1 hunks)
  • apps/docs/libraries/ts/sdk/keys/get.mdx (1 hunks)
🔇 Additional comments (4)
apps/docs/libraries/ex/functions/update_remaining.mdx (3)

Line range hint 6-6: LGTM: Good addition of function specification.

The added specification @spec update_remaining(map()) :: :ok provides clear information about the function's input and output types. This is a good practice in Elixir documentation and enhances the clarity of the API.


13-13: Excellent correction of the keyId description.

The change from "revoke" to "modify" in the keyId description accurately reflects the purpose of the update_remaining function. This correction aligns well with the PR objectives and addresses the documentation issue mentioned in #2211.


Line range hint 1-58: Summary: Documentation updates successfully address the reported issues.

The changes made to this file effectively address the issues mentioned in the PR objectives and the linked issue #2211:

  1. The function specification has been added, enhancing the clarity of the API documentation.
  2. The keyId parameter description has been corrected from "revoke" to "modify", accurately reflecting the function's purpose.

These updates improve the accuracy and consistency of the documentation for the update_remaining function. No further changes appear necessary in this file.

apps/docs/libraries/ts/sdk/keys/get.mdx (1)

9-9: Excellent update to the keyId description!

This change accurately reflects the purpose of the "Get" operation, which is to retrieve key information rather than to revoke a key. It directly addresses the issue mentioned in #2211 and aligns perfectly with the PR objectives of fixing incorrect descriptions in the documentation.

@chronark chronark merged commit e8cb10b into unkeyed:main Oct 5, 2024
6 of 10 checks passed
Copy link

oss-gg bot commented Oct 5, 2024

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

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.

[docs] Incorrect description for keyId in the sdk @unkey/api for get operation
2 participants