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

chore: Add RSS feed #2283

Merged
merged 2 commits into from
Oct 8, 2024
Merged

chore: Add RSS feed #2283

merged 2 commits into from
Oct 8, 2024

Conversation

perkinsjr
Copy link
Collaborator

@perkinsjr perkinsjr commented Oct 8, 2024

What does this PR do?

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

  • New Features
    • Introduced an RSS feed for the "Unkey" blog platform, allowing users to subscribe and receive updates.
  • Chores
    • Updated the application’s dependencies to include the new rss package and its type definitions.

Copy link

changeset-bot bot commented Oct 8, 2024

⚠️ No Changeset found

Latest commit: 17f5558

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 8, 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 8, 2024 7:57pm
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2024 7:57pm
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2024 7:57pm
workflows ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2024 7:57pm
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2024 7:57pm

Copy link
Contributor

coderabbitai bot commented Oct 8, 2024

📝 Walkthrough

Walkthrough

The changes introduce a new feature for generating an RSS feed for a blog platform called "Unkey." This is accomplished through the addition of a route.ts file that implements an asynchronous GET function to construct the RSS feed from blog post data. The package.json file is also updated to include a new dependency for the RSS functionality and its type definitions.

Changes

File Path Change Summary
apps/www/app/feed.xml/route.ts Added a new file that implements an asynchronous GET function to generate an RSS feed for blog posts.
apps/www/package.json Updated to include a new dependency "rss": "^1.2.2" and a devDependency "@types/rss": "^0.0.32".

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 8, 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: 1

🧹 Outside diff range and nitpick comments (3)
apps/www/app/feed.xml/route.ts (3)

1-12: LGTM with a minor suggestion.

The imports and RSS feed initialization look good. However, there's a small optimization we can make:

On line 8, replace the template literal with a regular string literal since there's no interpolation or special characters:

-  feed_url: `https://unkey.com/feed.xml`,
+  feed_url: "https://unkey.com/feed.xml",
🧰 Tools
🪛 Biome

[error] 8-8: Do not use template literals if interpolation and special-character handling are not needed.

Unsafe fix: Replace with string literal

(lint/style/noUnusedTemplateLiteral)


14-16: Consider removing redundant type annotations.

The sorting logic is correct, but we can simplify it by removing the redundant type annotations:

-const posts = allPosts.sort((a: Post, b: Post) => {
+const posts = allPosts.sort((a, b) => {
   return new Date(b.date).getTime() - new Date(a.date).getTime();
 });

The types of a and b are already inferred from allPosts, making the explicit Post annotations unnecessary.


18-30: Remove unnecessary async keyword and consider using forEach instead of map.

The GET function implementation looks good overall, but there are two minor improvements we can make:

  1. Remove the async keyword since there are no asynchronous operations inside the function:
-export async function GET() {
+export function GET() {
  1. Replace map with forEach since the return value of map is not being used:
-  posts.map((post) => {
+  posts.forEach((post) => {

These changes will make the code more accurate and efficient without changing its functionality.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 00213c6 and 17f5558.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • apps/www/app/feed.xml/route.ts (1 hunks)
  • apps/www/package.json (2 hunks)
🧰 Additional context used
🪛 Biome
apps/www/app/feed.xml/route.ts

[error] 8-8: Do not use template literals if interpolation and special-character handling are not needed.

Unsafe fix: Replace with string literal

(lint/style/noUnusedTemplateLiteral)

🔇 Additional comments (4)
apps/www/app/feed.xml/route.ts (2)

32-37: LGTM: Correct response generation.

The response generation is implemented correctly:

  • It uses the feed's XML output with proper indentation.
  • The content type is set appropriately for an Atom XML feed.

1-37: Overall, great implementation of the RSS feed feature!

The code successfully implements an RSS feed for the Unkey blog. It correctly imports necessary modules, initializes the feed with appropriate metadata, sorts posts, and generates feed items. The response is properly formatted as XML with the correct content type.

A few minor suggestions were made to optimize and improve the code:

  1. Removing a template literal where it's not needed.
  2. Removing redundant type annotations in the sort function.
  3. Removing the unnecessary async keyword and using forEach instead of map in the GET function.

These changes will make the code more efficient and accurate without altering its functionality. Great job on implementing this feature!

🧰 Tools
🪛 Biome

[error] 8-8: Do not use template literals if interpolation and special-character handling are not needed.

Unsafe fix: Replace with string literal

(lint/style/noUnusedTemplateLiteral)

apps/www/package.json (2)

55-55: Overall changes look good, with minor suggestions for improvement.

The additions to package.json are minimal and focused on adding RSS functionality, which aligns well with the PR objectives. The principle of minimal changes has been followed, which is commendable.

Consider the suggestions in the previous comments regarding package versions and alternatives. Once addressed, these changes should be ready for integration.

Also applies to: 74-74


74-74: Verify type definition compatibility with the main package.

Adding type definitions for the rss package is a good practice for TypeScript projects. However, please ensure that the version of @types/rss (0.0.32) is compatible with the version of rss (1.2.2) you're using.

To verify the compatibility, you can run the following command:

If there's a significant discrepancy, consider updating both packages to their latest compatible versions.

@@ -52,6 +52,7 @@
"react-syntax-highlighter": "^15.5.0",
"rehype-raw": "^7.0.0",
"remark-gfm": "^3.0.1",
"rss": "^1.2.2",
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider using a more up-to-date RSS library.

The addition of the rss package aligns with the PR objective of adding an RSS feed. However, version 1.2.2 is quite old (last updated in 2017). Consider using a more modern alternative or a newer version if available. Some options to explore:

  1. feed (https://www.npmjs.com/package/feed)
  2. rss-generator (https://www.npmjs.com/package/rss-generator)
  3. Check if there's a newer version of rss that's compatible with your project

Would you like me to research and suggest a specific alternative with an example of how to integrate it?

@perkinsjr perkinsjr merged commit f781b9c into main Oct 8, 2024
26 of 28 checks passed
@perkinsjr perkinsjr deleted the rss-feed branch October 8, 2024 20:10
@coderabbitai coderabbitai bot mentioned this pull request Oct 10, 2024
18 tasks
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