Skip to content

Remove duplicate definition of primaryKey from example in a case study #1804

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bavulapati
Copy link

@bavulapati bavulapati commented Aug 4, 2025

What kind of change does this PR introduce?
Docs

Issue Number:

  • Others? Found this while browsing the website. I do not have an Issue Number.

Summary

In the example json schema, the primaryKey is defined twice. Retained the second instance, as it is after the appropriate comment.

Does this PR introduce a breaking change?

No

Checklist

Please ensure the following tasks are completed before submitting this pull request.

In the example json schema, the primaryKey is defined twice. Retained
the second instance, as it is after the appropriate comment.

Signed-off-by: Balakrishna Avulapati <[email protected]>
@bavulapati bavulapati requested a review from a team as a code owner August 4, 2025 12:45
@github-project-automation github-project-automation bot moved this to Ready to review in PR - Triage Group Aug 4, 2025
Copy link

github-actions bot commented Aug 4, 2025

Hi @bavulapati! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

Copy link

github-actions bot commented Aug 4, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
website ✅ Ready (View Log) Visit Preview dcbeaea

Copy link

codecov bot commented Aug 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (b63b163) to head (dcbeaea).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1804   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           30        30           
  Lines          633       633           
  Branches       196       196           
=========================================
  Hits           633       633           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

github-actions bot commented Aug 4, 2025

Hi @bavulapati! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready to review
Development

Successfully merging this pull request may close these issues.

1 participant