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 /ffxiv/craftsim crawl #512

Merged
merged 2 commits into from
Oct 23, 2024
Merged

fix /ffxiv/craftsim crawl #512

merged 2 commits into from
Oct 23, 2024

Conversation

cohenaj194
Copy link
Contributor

@cohenaj194 cohenaj194 commented Oct 23, 2024

Summary by CodeRabbit

  • New Features
    • Updated robots.txt to disallow web crawlers from accessing a broader path, enhancing site privacy and control over indexed content.
    • Improved XML sitemap generation with dynamic URLs for World of Warcraft and Final Fantasy XIV items, ensuring better indexing of relevant content.
    • Commented out specific URL entries in the sitemap for potential future reintroduction.

Copy link
Contributor

coderabbitai bot commented Oct 23, 2024

Walkthrough

The changes involve modifications to the robots.txt loader function in the app/routes/[robots.txt].tsx file, specifically updating the Disallow directive from /ffxiv/craftsim/queries to /ffxiv/craftsim. Additionally, the sitemap.xml loader function in app/routes/[sitemap.xml].tsx has been altered to comment out specific <url> entries related to World of Warcraft items and implement dynamic URL generation for both WoW and Final Fantasy XIV items. The overall structure and response handling of both loader functions remain unchanged.

Changes

File Change Summary
app/routes/[robots.txt].tsx Updated Disallow directive from /ffxiv/craftsim/queries to /ffxiv/craftsim. Loader function structure remains unchanged.
app/routes/[sitemap.xml].tsx Commented out specific <url> entries for WoW items. Implemented dynamic URL generation for WoW and FFXIV items. Loader function structure remains unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant UserAgent as User Agent
    participant Loader as Loader Function
    participant RobotsTxt as robots.txt

    UserAgent->>Loader: Request robots.txt
    Loader->>RobotsTxt: Generate robotText
    RobotsTxt-->>Loader: Return robotText
    Loader-->>UserAgent: Send robots.txt response
Loading
sequenceDiagram
    participant UserAgent as User Agent
    participant Loader as Loader Function
    participant Sitemap as sitemap.xml

    UserAgent->>Loader: Request sitemap.xml
    Loader->>Sitemap: Generate XML with dynamic URLs
    Sitemap-->>Loader: Return XML document
    Loader-->>UserAgent: Send sitemap.xml response
Loading

🐰 "In the garden where the bunnies hop,
We’ve tidied up the rules, no need to stop.
With paths now clear for crawlers to see,
A new directive for all to agree.
So hop along, dear web, take your flight,
Our little changes make things just right!"
🌼


🪧 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

cloudflare-workers-and-pages bot commented Oct 23, 2024

Deploying saddlebag-with-pockets with  Cloudflare Pages  Cloudflare Pages

Latest commit: fb8265c
Status: ✅  Deploy successful!
Preview URL: https://fece11ef.saddlebag-with-pockets.pages.dev
Branch Preview URL: https://fix-robot.saddlebag-with-pockets.pages.dev

View logs

@cohenaj194 cohenaj194 enabled auto-merge (squash) October 23, 2024 02:44
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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3e362aa and 0677e9a.

📒 Files selected for processing (1)
  • app/routes/[robots.txt].tsx (1 hunks)
🧰 Additional context used

app/routes/[robots.txt].tsx Show resolved Hide resolved
Copy link

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)
app/routes/[sitemap.xml].tsx (1)

Line range hint 1-3: Consider implementing sitemap pagination for better performance.

The current implementation generates URLs for all items at once, which could lead to very large sitemap files. Consider implementing sitemap pagination following Google's guidelines:

  1. Split sitemaps into smaller files (max 50,000 URLs or 50MB per file)
  2. Create a sitemap index file
  3. Consider different update frequencies for static vs dynamic content

Example implementation of a sitemap index:

// sitemapIndex.xml.tsx
export const loader: LoaderFunction = async () => {
  const baseURL = 'https://saddlebagexchange.com'
  const currentDate = new Date().toISOString()
  
  return new Response(
    `<?xml version="1.0" encoding="UTF-8"?>
    <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
      <sitemap>
        <loc>${baseURL}/static-pages-sitemap.xml</loc>
        <lastmod>${currentDate}</lastmod>
      </sitemap>
      <sitemap>
        <loc>${baseURL}/wow-items-sitemap.xml</loc>
        <lastmod>${currentDate}</lastmod>
      </sitemap>
      <sitemap>
        <loc>${baseURL}/ffxiv-items-sitemap.xml</loc>
        <lastmod>${currentDate}</lastmod>
      </sitemap>
    </sitemapindex>`,
    {
      status: 200,
      headers: {
        'Content-Type': 'application/xml'
      }
    }
  )
}

Also applies to: 14-15

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0677e9a and fb8265c.

📒 Files selected for processing (1)
  • app/routes/[sitemap.xml].tsx (2 hunks)
🧰 Additional context used
🔇 Additional comments (2)
app/routes/[sitemap.xml].tsx (2)

184-203: Verify the impact of removing multiple feature URLs from sitemap.

Several important URLs have been commented out, including /ffxiv/craftsim which aligns with the PR objective. However, the removal of other URLs (/queries/full-scan, /ffxiv/marketshare, /wow/best-deals) needs verification:

  1. Are these features being deprecated?
  2. Will this impact user accessibility to these features?
  3. Is this coordinated with the frontend navigation updates?

119-128: Verify the intentional removal of WoW export and marketshare URLs from sitemap.

These URLs have been commented out rather than deleted. Please clarify if this is intentional and if these features are being deprecated or replaced.

@cohenaj194 cohenaj194 disabled auto-merge October 23, 2024 12:03
@cohenaj194 cohenaj194 merged commit 25c7783 into master Oct 23, 2024
5 checks passed
@cohenaj194 cohenaj194 deleted the fix/robot branch October 23, 2024 12:03
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.

1 participant