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

feat(rest-api): adds path to route request #3231

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

abtestingalpha
Copy link
Collaborator

@abtestingalpha abtestingalpha commented Oct 4, 2024

Summary by CodeRabbit

  • New Features
    • Enhanced logging functionality to include request paths in log messages for incoming requests and outgoing responses.
    • Conditional truncation of outgoing response logs for specific paths to protect sensitive information.

Copy link
Contributor

coderabbitai bot commented Oct 4, 2024

Walkthrough

The changes in this pull request focus on enhancing the logging functionality within an Express application. The log messages for incoming requests and outgoing responses have been modified to include the request path dynamically. Additionally, the outgoing response logs are now conditionally truncated for specific paths to avoid logging sensitive or large payloads. The overall middleware structure remains unchanged.

Changes

File Change Summary
packages/rest-api/src/app.ts Updated incoming request log to include request path; modified outgoing response log to include original request path; added conditional truncation for specific paths.

Possibly related PRs

  • rest-api(fix): Denest keys for logs #3230: The changes in this PR also focus on modifying the logging functionality within the Express application, specifically altering the structure of log messages for incoming requests and outgoing responses, which directly relates to the logging enhancements made in the main PR.

Suggested labels

size/xs, Sol, Typescript

Suggested reviewers

  • trajan0x
  • Defi-Moses

Poem

In the code where rabbits hop,
Logs now show the path non-stop.
Requests and responses, clear as day,
With paths included, come what may!
Truncating logs, a clever trick,
Keeping secrets safe and slick! 🐇✨


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.

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

🧹 Outside diff range and nitpick comments (1)
packages/rest-api/src/app.ts (1)

Line range hint 27-33: Enhanced logging for outgoing responses with payload size consideration

Great improvements to the outgoing response logging:

  1. Including ${originalPath} in the log message enhances traceability.
  2. Conditionally truncating the response body for specific paths ('/' and '/tokenlist') is a good practice to prevent logging sensitive or large payloads.

These changes align well with the PR objective and improve the overall logging strategy.

Minor suggestion: Consider using case-insensitive comparison for the '/tokenlist' path to ensure consistent behavior. You can modify the condition as follows:

- originalPath === '/' || originalPath.toLowerCase() === '/tokenlist'
+ originalPath === '/' || originalPath.toLowerCase() === '/tokenlist'.toLowerCase()

This change ensures that variations like '/TokenList' or '/TOKENLIST' are also captured.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 911d778 and 189b572.

📒 Files selected for processing (1)
  • packages/rest-api/src/app.ts (2 hunks)
🔇 Additional comments (2)
packages/rest-api/src/app.ts (2)

15-15: Improved logging for incoming requests

The addition of ${req.path} to the log message enhances the logging detail, making it easier to track and debug incoming requests. This change aligns well with the PR objective of adding path to route requests.


Line range hint 1-78: Summary: Improved request and response logging

The changes in this PR successfully enhance the logging capabilities of the Express application by including the request path in both incoming and outgoing log messages. This improvement aligns well with the PR objective of adding path to route requests.

Key improvements:

  1. More detailed logging for incoming requests
  2. Enhanced traceability for outgoing responses
  3. Consideration for payload size in response logging

These changes will significantly aid in debugging and monitoring the application's behavior. No major issues were found, and the modifications are focused without introducing any breaking changes or security risks.

Great job on improving the logging functionality!

Copy link

codecov bot commented Oct 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.43902%. Comparing base (7a0c7e7) to head (189b572).
Report is 2 commits behind head on master.

Additional details and impacted files
@@              Coverage Diff              @@
##              master       #3231   +/-   ##
=============================================
  Coverage   90.43902%   90.43902%           
=============================================
  Files             54          54           
  Lines           1025        1025           
  Branches          82          82           
=============================================
  Hits             927         927           
  Misses            95          95           
  Partials           3           3           
Flag Coverage Δ
packages 90.43902% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

Deploying sanguine-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 189b572
Status: ✅  Deploy successful!
Preview URL: https://965da455.sanguine-fe.pages.dev
Branch Preview URL: https://rest-api-adds-meta.sanguine-fe.pages.dev

View logs

@abtestingalpha abtestingalpha merged commit b3883c0 into master Oct 4, 2024
36 checks passed
@abtestingalpha abtestingalpha deleted the rest-api/adds-meta branch October 4, 2024 17:51
Copy link

codecov bot commented Oct 4, 2024

Bundle Report

Bundle size has no change ✅

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

Successfully merging this pull request may close these issues.

1 participant