fix: token utility export

[DanielRivers]

Explain your changes

fix: token utilities were not exported
fix: test on exports

Checklist

• I have read the “Pull requests” section in the contributing guidelines.
• I agree to the terms within the code of conduct.

🛟 If you need help, consider asking for advice over in the Kinde community.

[coderabbitai]

Walkthrough

The changes involve updates to the test suite for the index exports in lib/main.test.ts, where the expected exports are redefined to include additional token utility functions. Additionally, the lib/main.ts file now exports all entities from the utils/token module, expanding the publicly accessible exports. A minor change in lib/utils/token/index.ts introduces a blank line without affecting functionality.

Changes

File(s)	Change Summary
lib/main.test.ts	Restructured test cases for index exports; updated expectedExports to include additional token utility functions.
lib/main.ts	Added export statement for all entities from ./utils/token.
lib/utils/token/index.ts	Added a blank line after import statements; no functional changes made.

Possibly related PRs

• feat: add expo-secure-store #5: The changes in this PR involve modifications to the lib/main.test.ts file, specifically updating the expected exports in the test suite, which is directly related to the restructuring of the test case for exported entities in the main PR.

Suggested reviewers

• DaveOrDead

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3ee4b53 and 1fe6d7e.

Files selected for processing (1)

• lib/main.ts (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• lib/main.ts

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.31%. Comparing base (1f4f108) to head (1fe6d7e).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   76.27%   76.31%   +0.04%     
==========================================
  Files          27       27              
  Lines         531      532       +1     
  Branches       82       82              
==========================================
+ Hits          405      406       +1     
  Misses        126      126              

Files with missing lines	Coverage Δ
lib/main.ts	100.00% <100.00%> (ø)
lib/utils/token/index.ts	100.00% <ø> (ø)

[coderabbitai]

Actionable comments posted: 1

Outside diff range and nitpick comments (1)

lib/main.test.ts (1)

Line range hint 29-61: LGTM! Consider adding a comment for maintainability.

The changes align well with the PR objectives of fixing token utility exports. The updated list of expected exports now includes all the token utility functions, ensuring they are correctly exported from the main module.

Consider adding a comment above the expectedExports array to explain why it's hardcoded and how to maintain it. This will help future developers understand the reasoning behind this approach. For example:

// Hardcoded list of expected exports for explicit visibility.
// Update this list when adding or removing exports from the main module.
const expectedExports = [
  // ... (existing list)
];

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1f4f108 and 3ee4b53.

Files selected for processing (3)

• lib/main.test.ts (2 hunks)
• lib/main.ts (1 hunks)
• lib/utils/token/index.ts (1 hunks)

Files skipped from review due to trivial changes (1)

• lib/utils/token/index.ts