Add json extension for a valid content-type

[scosman]

This also tells Cloudflare to gzip the content: https://developers.cloudflare.com/speed/optimization/content/brotli/content-compression/

Also: give more relevance to title and description over body

Summary by CodeRabbit

• New Features

  • Enhanced search functionality with improved result scoring based on title, description, and body.
  • Updated API endpoint to provide results in JSON format.

• Bug Fixes

  • Clarified output file format for the search index, ensuring it is explicitly saved as api.json.

[coderabbitai]

Walkthrough

The recent changes enhance the search functionality of the Svelte application and clarify the output format of the index building process. The search feature now supports weighted keys, improving result relevance. Additionally, file paths have been updated to specify JSON formats, reinforcing data clarity and interoperability across systems. These modifications collectively aim to provide a more robust user experience and refined data handling.

Changes

Files	Change Summary
src/lib/build_index.ts	Updated output file name from api to api.json in fs.writeFileSync, clarifying the data format.
src/routes/(marketing)/search/+page.svelte	Enhanced search functionality by modifying fuseOptions to include weighted keys; updated API endpoint to "/search/api.json".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SearchComponent
    participant API

    User->>SearchComponent: Perform search
    SearchComponent->>API: Fetch results from /search/api.json
    API-->>SearchComponent: Return JSON search results
    SearchComponent->>User: Display weighted search results

Loading

🐰 In the garden, changes bloom,
A search so bright, dispelling gloom.
With weights to guide and paths refined,
JSON whispers, clarity aligned.
Hop along, let data play,
In this new world, we’ll find our way! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2b62ca4 and 2f199e0.

Files selected for processing (2)

• src/lib/build_index.ts (1 hunks)
• src/routes/(marketing)/search/+page.svelte (2 hunks)

Additional comments not posted (3)

src/lib/build_index.ts (1)

73-75: LGTM! The change to specify JSON format for the output file is clear and improves interoperability.

The code changes are approved.

src/routes/(marketing)/search/+page.svelte (2)

10-14: LGTM! The weighted keys in fuseOptions enhance the relevance of search results.

The code changes are approved.

---

25-25: LGTM! The update to the API endpoint aligns with the new output file format.

The code changes are approved.