Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThis PR adds numerous new blog posts as Markdoc pages under src/routes/blog/post, each with front matter and full article content on topics like backend comparisons, compliance, scaling, self-hosting, and Appwrite guidance. The .optimize-cache.json has many new image entries for blog covers and contains unresolved Git merge conflict markers (<<<<<<<, =======, >>>>>>>) that must be resolved. No runtime code or public API signatures were modified. Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…bsite into add-new-blogs-aditya
… cover images for new posts
Contributor
Greptile SummaryThis PR adds 27 new blog posts covering backend development topics (authentication, databases, storage, compliance, tooling comparisons) along with their corresponding cover images. The posts are well-written and informative, but several code examples contain incorrect Appwrite SDK references that would mislead readers attempting to follow them. Key issues found:
Confidence Score: 2/5
Important Files Changed
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
src/routes/blog/post/cloudinary-vs-appwrite-storage/+page.markdoc
Outdated
Show resolved
Hide resolved
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 13
🧹 Nitpick comments (4)
src/routes/blog/post/baa-explained/+page.markdoc (1)
86-87: Remove repeated BAA-relationship sentenceThe same “primary BAA relationship becomes the underlying cloud provider…” point is repeated almost verbatim in two places. Keep it once for tighter flow.
Also applies to: 92-93
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/baa-explained/`+page.markdoc around lines 86 - 87, Two identical sentences repeat the same point; remove one occurrence of the sentence "The primary BAA relationship becomes the underlying cloud provider where Appwrite runs, not a separate backend vendor with its own sub-processors and data handling policies." (it appears twice) so the page keeps the statement only once for tighter flow, and adjust surrounding punctuation/spacing so the paragraph reads smoothly after deleting the duplicate.src/routes/blog/post/evaluate-backend-tools-no-lock-in/+page.markdoc (1)
109-117: Avoid absolute migration claims to reduce overpromise risk.“Without any code changes” is very strong and may not hold for all deployments/integrations. Consider softening to “minimal or no application code changes,” depending on setup.
📝 Suggested wording adjustment
-- **Open source and self-hosting**: Appwrite is Apache 2.0 licensed and fully self-hostable. If Appwrite Cloud ceased to exist, you could operate the same software on your own infrastructure without any code changes. +- **Open source and self-hosting**: Appwrite is Apache 2.0 licensed and fully self-hostable. If Appwrite Cloud ceased to exist, you could operate the same software on your own infrastructure with minimal or no application code changes. ... -[Appwrite](https://appwrite.io) is designed to minimize these concerns: it's open source (Apache 2.0 licensed), fully self-hostable, uses standard REST APIs alongside native SDKs, stores data in portable formats, and offers a managed cloud service ([Appwrite Cloud](https://cloud.appwrite.io)) that can be migrated to self-hosted without code changes. It's a deliberate choice for teams that want a capable backend platform without accepting deep vendor lock-in. +[Appwrite](https://appwrite.io) is designed to minimize these concerns: it's open source (Apache 2.0 licensed), fully self-hostable, uses standard REST APIs alongside native SDKs, stores data in portable formats, and offers a managed cloud service ([Appwrite Cloud](https://cloud.appwrite.io)) that can typically be migrated to self-hosted with minimal application code changes. It's a deliberate choice for teams that want a capable backend platform without accepting deep vendor lock-in.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/evaluate-backend-tools-no-lock-in/`+page.markdoc around lines 109 - 117, Replace the absolute claim “without any code changes” with a softened, qualified phrase to avoid overpromising—e.g., change the sentence in the Appwrite description that currently reads “If Appwrite Cloud ceased to exist, you could operate the same software on your own infrastructure without any code changes.” to something like “you could typically operate the same software on your own infrastructure with minimal or no application code changes, depending on your deployment and integrations,” so the text now qualifies the migration outcome and references the original quoted phrase for locating the edit.src/routes/blog/post/when-custom-backend-stops-being-worth-it/+page.markdoc (1)
18-67: Prefer##for in-article section headings.These sections are currently top-level
#headings. Iflayout: postrenders the page title as H1, demoting section headings to H2 keeps a clean semantic hierarchy.Suggested heading-level adjustment
-# What "custom backend" actually costs +## What "custom backend" actually costs -# Signs that a custom backend is costing more than it's worth +## Signs that a custom backend is costing more than it's worth -# When custom backends are still the right choice +## When custom backends are still the right choice -# What the migration actually looks like +## What the migration actually looks like -# Appwrite as your managed backend +## Appwrite as your managed backend -# Migrate away from your custom backend before it becomes a blocker +## Migrate away from your custom backend before it becomes a blocker🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/when-custom-backend-stops-being-worth-it/`+page.markdoc around lines 18 - 67, The article uses top-level H1 headings (#) for in-article sections such as "What \"custom backend\" actually costs", "Signs that a custom backend is costing more than it's worth", "When custom backends are still the right choice", "What the migration actually looks like", "Appwrite as your managed backend", and "Migrate away from your custom backend before it becomes a blocker"; because the page's layout likely renders the title as H1, change each of these in-article headings from single '#' to '##' so they become H2s (keep the exact text and formatting, only replace the leading '#' with '##') to preserve semantic hierarchy and accessibility.src/routes/blog/post/open-source-baas-alternatives/+page.markdoc (1)
26-44: Use consistent heading depth for the “Appwrite” section.Promoting this heading to
##keeps hierarchy aligned with the surrounding sections and improves TOC structure.✏️ Proposed tweak
-# Appwrite as a BaaS alternative +## Appwrite as a BaaS alternative🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/open-source-baas-alternatives/`+page.markdoc around lines 26 - 44, The "Appwrite as a BaaS alternative" heading is using a level-1 header; change its markdown heading to level-2 (i.e., promote "# Appwrite as a BaaS alternative" to "## Appwrite as a BaaS alternative") so it matches the surrounding "## Other open-source options" and "## Supabase" sections and keeps the TOC and hierarchy consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.optimize-cache.json:
- Around line 264-269: The .optimize-cache.json file contains leftover Git
conflict markers (<<<<<<<, =======, >>>>>>>) which breaks JSON parsing; open
.optimize-cache.json, remove the conflict markers and resolve to a single valid
entry for the conflicting key (choose the correct image key/value you intend to
keep), ensure commas and surrounding braces remain valid JSON, save the file,
then run the script that calls load_cache() (in scripts/optimize-assets.js) to
verify main() can parse the cache successfully.
In `@src/routes/blog/post/appwrite-vs-vercel-vs-netlify/`+page.markdoc:
- Around line 76-87: The example imports Databases but instantiates a
non-existent TablesDB, causing ReferenceError; replace the TablesDB
instantiation with the correct SDK class (use new Databases(client) instead of
new TablesDB(client)) and then call the appropriate Databases method (replace
tablesDB.listRows(...) with the Databases API call if needed) so the symbols
Client, Account, Databases, account.get, and the database list call match the
SDK.
In `@src/routes/blog/post/avoid-backend-overengineering/`+page.markdoc:
- Line 5: The frontmatter date is set to a future day ("date: 2026-03-19");
confirm whether the post should be scheduled or published now and, if immediate
publication is intended, change the "date" field in the +page.markdoc
frontmatter to today's date (e.g., "2026-03-18") or the desired publish
timestamp; if the future date is intentional for scheduling, add a short
comment/note in the file or PR explaining that the future date is deliberate so
reviewers know it’s not a mistake.
In `@src/routes/blog/post/baa-explained/`+page.markdoc:
- Around line 44-45: Replace the overly broad bullet "Breach notification
obligations and timelines: HIPAA requires notifying affected individuals within
60 days of discovering a breach" under the "Breach notification obligations"
heading with a narrower, accurate statement: indicate that breach notification
timing varies by role and law (e.g., generally “without unreasonable delay” for
business associates and specific 60‑day HITECH timelines for covered entities
where applicable), and keep the "Sub-contractor requirements" bullet about
downstream vendors signing BAAs; update the phrasing to avoid asserting a
universal 60‑day rule and instead reference role‑based and statute‑specific
timing.
- Around line 86-93: Summary: The text in the "Build your HIPAA-compliant
backend with full data control" section makes absolute claims ("data never
leaves your controlled environment" and "primary BAA relationship becomes the
underlying cloud provider") that ignore common third‑party services and
configuration choices. Fix: in +page.markdoc, update the paragraph and the
sentence containing "data never leaves your controlled environment" and the
repeated BAA claim to be conditional—add explicit assumptions and examples
(e.g., email/SMS providers, analytics/monitoring, backups, third‑party
integrations, support tooling) and state that self‑hosting reduces risk only
when those services are configured to keep PHI in‑scope; include a short
checklist or qualifier phrase like "assuming you do not use external processors
for X,Y,Z and have contractual BAAs in place" and remove absolute language so
the claims read as qualified benefits rather than guarantees.
In `@src/routes/blog/post/build-from-scratch-productivity/`+page.markdoc:
- Line 5: The post frontmatter currently sets date: 2026-03-19 which schedules
the article for tomorrow; confirm whether this future publish date is
intentional and if not, update the frontmatter "date" field in +page.markdoc to
either the intended publish date or today's date (2026-03-18) so blog
listing/order is correct, or explicitly note scheduling elsewhere if you want it
to remain future-dated.
- Around line 71-74: Replace the absolute claim "implemented correctly and
maintained by the Appwrite team, not yours." in the Authentication bullet with
softer, verifiable phrasing—e.g., "designed following best practices and
maintained by the Appwrite team"—and add a link to the relevant Appwrite docs or
security page; also scan nearby bullets for other absolute language (like "No S3
configuration" / "No custom API layer") and reword to less categorical if
present, e.g., "reduces the need for..." while adding documentation links for
verification.
In `@src/routes/blog/post/build-internal-tools-quickly/`+page.markdoc:
- Around line 104-117: The snippet uses the variable client when constructing
new Functions(client) and calling functions.createExecution, but client is not
initialized; add a Client initialization (e.g., create a new Client instance and
configure endpoint/project/API key) before the line const functions = new
Functions(client) so the Client is defined and authenticated for
functions.createExecution to work.
In `@src/routes/blog/post/easiest-file-uploads/`+page.markdoc:
- Around line 44-61: The sample is missing the Permission and Role symbols used
in the storage.createBucket call, causing a ReferenceError; update the import
that currently imports Client and Storage to also import Permission and Role
from 'node-appwrite' so Permission.read/create/update/delete and Role.user are
in scope for the bucket creation code (refer to the existing import line and the
storage.createBucket usage).
In `@src/routes/blog/post/evaluate-backend-tools-no-lock-in/`+page.markdoc:
- Line 71: Change the confusing heading text "The migration path from the
alternative" to "The migration path to an alternative" in the Markdoc page;
locate the heading line that currently reads "## 5. The migration path from the
alternative" and replace it with "## 5. The migration path to an alternative",
and if other content or internal links rely on the heading slug/anchor, update
those references accordingly to match the new heading text.
In `@src/routes/blog/post/save-weeks-managed-backends/`+page.markdoc:
- Around line 5-11: The post is dated 2026-03-19 but setting unlisted: true does
not prevent RSS exposure; update the metadata to avoid accidental early
publishing by either (A) removing or backdating the date field (the "date"
frontmatter) and only adding the March 19, 2026 date when you merge on/after
that date, or (B) keep this file out of the content tree until March 19, 2026;
do not rely on "unlisted: true" alone to keep it private (the "unlisted"
frontmatter only hides the index, not RSS).
In
`@src/routes/blog/post/self-hosting-with-appwrite-benefits-setup-and-best-practices/`+page.markdoc:
- Around line 64-65: Update the sentence that reads "Appwrite generates TLS
certificates automatically using your configured hostname" to qualify automatic
TLS issuance by listing required prerequisites: public domain with a valid TLD,
production mode (_APP_ENV=production), a configured
_APP_SYSTEM_SECURITY_EMAIL_ADDRESS, and internet-reachable ports 80 and 443;
also note that IP-only or internal-network setups cannot obtain Let's Encrypt
certs automatically and must use manual certificates or a proxy. Locate and
replace the line in the paragraph starting with "Enforce HTTPS." / the sentence
about Appwrite generating TLS certificates automatically and ensure the new text
clearly states these prerequisites and fallback options.
- Around line 104-106: Update the sentence "The APIs and SDKs are identical
between Cloud and self-hosted instances." to clarify parity is
version-dependent: explicitly state that parity holds when Cloud and self-hosted
versions match and note that Appwrite Cloud may receive features earlier (with
self-hosted updates typically following later), so API/SDK parity is not
unconditional. Keep the rest of the paragraph intact and use wording similar to
"APIs and SDKs are effectively identical when running the same Appwrite version;
however, Cloud can receive features earlier, so parity depends on matching
versions."
---
Nitpick comments:
In `@src/routes/blog/post/baa-explained/`+page.markdoc:
- Around line 86-87: Two identical sentences repeat the same point; remove one
occurrence of the sentence "The primary BAA relationship becomes the underlying
cloud provider where Appwrite runs, not a separate backend vendor with its own
sub-processors and data handling policies." (it appears twice) so the page keeps
the statement only once for tighter flow, and adjust surrounding
punctuation/spacing so the paragraph reads smoothly after deleting the
duplicate.
In `@src/routes/blog/post/evaluate-backend-tools-no-lock-in/`+page.markdoc:
- Around line 109-117: Replace the absolute claim “without any code changes”
with a softened, qualified phrase to avoid overpromising—e.g., change the
sentence in the Appwrite description that currently reads “If Appwrite Cloud
ceased to exist, you could operate the same software on your own infrastructure
without any code changes.” to something like “you could typically operate the
same software on your own infrastructure with minimal or no application code
changes, depending on your deployment and integrations,” so the text now
qualifies the migration outcome and references the original quoted phrase for
locating the edit.
In `@src/routes/blog/post/open-source-baas-alternatives/`+page.markdoc:
- Around line 26-44: The "Appwrite as a BaaS alternative" heading is using a
level-1 header; change its markdown heading to level-2 (i.e., promote "#
Appwrite as a BaaS alternative" to "## Appwrite as a BaaS alternative") so it
matches the surrounding "## Other open-source options" and "## Supabase"
sections and keeps the TOC and hierarchy consistent.
In `@src/routes/blog/post/when-custom-backend-stops-being-worth-it/`+page.markdoc:
- Around line 18-67: The article uses top-level H1 headings (#) for in-article
sections such as "What \"custom backend\" actually costs", "Signs that a custom
backend is costing more than it's worth", "When custom backends are still the
right choice", "What the migration actually looks like", "Appwrite as your
managed backend", and "Migrate away from your custom backend before it becomes a
blocker"; because the page's layout likely renders the title as H1, change each
of these in-article headings from single '#' to '##' so they become H2s (keep
the exact text and formatting, only replace the leading '#' with '##') to
preserve semantic hierarchy and accessibility.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 41f6ff7a-5191-4bb1-96c2-da50adfed8c2
⛔ Files ignored due to path filters (26)
static/images/blog/agency-backend-standardization/cover.pngis excluded by!**/*.pngstatic/images/blog/appwrite-for-startups-ship-faster-without-backend-headaches/cover.pngis excluded by!**/*.pngstatic/images/blog/appwrite-vs-vercel-vs-netlify/cover.pngis excluded by!**/*.pngstatic/images/blog/avoid-backend-overengineering/cover.pngis excluded by!**/*.pngstatic/images/blog/baa-explained/cover.pngis excluded by!**/*.pngstatic/images/blog/backend-platform-security-responsibilities/cover.pngis excluded by!**/*.pngstatic/images/blog/backend-that-scales/cover.pngis excluded by!**/*.pngstatic/images/blog/build-from-scratch-productivity/cover.pngis excluded by!**/*.pngstatic/images/blog/build-internal-tools-quickly/cover.pngis excluded by!**/*.pngstatic/images/blog/building-a-production-ready-backend-with-appwrite/cover.pngis excluded by!**/*.pngstatic/images/blog/client-dashboards-internal-tools/cover.pngis excluded by!**/*.pngstatic/images/blog/cloudinary-vs-appwrite-storage/cover.pngis excluded by!**/*.pngstatic/images/blog/compliant-architectures/cover.pngis excluded by!**/*.pngstatic/images/blog/developer-compliance-thinking/cover.pngis excluded by!**/*.pngstatic/images/blog/easiest-file-uploads/cover.pngis excluded by!**/*.pngstatic/images/blog/evaluate-backend-tools-no-lock-in/cover.pngis excluded by!**/*.pngstatic/images/blog/firebase-vs-open-source-tradeoffs/cover.pngis excluded by!**/*.pngstatic/images/blog/how-appwrite-simplifies-backend-development-for-frontend-devs/cover.pngis excluded by!**/*.pngstatic/images/blog/indie-hackers-shipping-faster/cover.pngis excluded by!**/*.pngstatic/images/blog/open-source-baas-alternatives/cover.pngis excluded by!**/*.pngstatic/images/blog/open-source-backend-vs-managed-saas/cover.pngis excluded by!**/*.pngstatic/images/blog/open-source-regulated-environments/cover.pngis excluded by!**/*.pngstatic/images/blog/save-weeks-managed-backends/cover.pngis excluded by!**/*.pngstatic/images/blog/secure-user-data-non-expert/cover.pngis excluded by!**/*.pngstatic/images/blog/self-hosting-with-appwrite-benefits-setup-and-best-practices/cover.pngis excluded by!**/*.pngstatic/images/blog/when-custom-backend-stops-being-worth-it/cover.pngis excluded by!**/*.png
📒 Files selected for processing (27)
.optimize-cache.jsonsrc/routes/blog/post/agency-backend-standardization/+page.markdocsrc/routes/blog/post/appwrite-for-startups-ship-faster-without-backend-headaches/+page.markdocsrc/routes/blog/post/appwrite-vs-vercel-vs-netlify/+page.markdocsrc/routes/blog/post/avoid-backend-overengineering/+page.markdocsrc/routes/blog/post/baa-explained/+page.markdocsrc/routes/blog/post/backend-platform-security-responsibilities/+page.markdocsrc/routes/blog/post/backend-that-scales/+page.markdocsrc/routes/blog/post/build-from-scratch-productivity/+page.markdocsrc/routes/blog/post/build-internal-tools-quickly/+page.markdocsrc/routes/blog/post/building-a-production-ready-backend-with-appwrite/+page.markdocsrc/routes/blog/post/client-dashboards-internal-tools/+page.markdocsrc/routes/blog/post/cloudinary-vs-appwrite-storage/+page.markdocsrc/routes/blog/post/compliant-architectures/+page.markdocsrc/routes/blog/post/developer-compliance-thinking/+page.markdocsrc/routes/blog/post/easiest-file-uploads/+page.markdocsrc/routes/blog/post/evaluate-backend-tools-no-lock-in/+page.markdocsrc/routes/blog/post/firebase-vs-open-source-tradeoffs/+page.markdocsrc/routes/blog/post/how-appwrite-simplifies-backend-development-for-frontend-devs/+page.markdocsrc/routes/blog/post/indie-hackers-shipping-faster/+page.markdocsrc/routes/blog/post/open-source-baas-alternatives/+page.markdocsrc/routes/blog/post/open-source-backend-vs-managed-saas/+page.markdocsrc/routes/blog/post/open-source-regulated-environments/+page.markdocsrc/routes/blog/post/save-weeks-managed-backends/+page.markdocsrc/routes/blog/post/secure-user-data-non-expert/+page.markdocsrc/routes/blog/post/self-hosting-with-appwrite-benefits-setup-and-best-practices/+page.markdocsrc/routes/blog/post/when-custom-backend-stops-being-worth-it/+page.markdoc
src/routes/blog/post/appwrite-vs-vercel-vs-netlify/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/avoid-backend-overengineering/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/evaluate-backend-tools-no-lock-in/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/self-hosting-with-appwrite-benefits-setup-and-best-practices/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/self-hosting-with-appwrite-benefits-setup-and-best-practices/+page.markdoc
Outdated
Show resolved
Hide resolved
…-and-best-practices/+page.markdoc Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…-and-best-practices/+page.markdoc Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…-backend-headaches/+page.markdoc
src/routes/blog/post/firebase-vs-open-source-tradeoffs/+page.markdoc
Outdated
Show resolved
Hide resolved
…-backend-headaches/+page.markdoc
…s/+page.markdoc Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
…kdoc Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
…appwrite/+page.markdoc Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
src/routes/blog/post/indie-hackers-shipping-faster/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/open-source-baas-alternatives/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/open-source-backend-vs-managed-saas/+page.markdoc
Outdated
Show resolved
Hide resolved
src/routes/blog/post/self-hosting-with-appwrite-benefits-setup-and-best-practices/+page.markdoc
Outdated
Show resolved
Hide resolved
adityaoberai
commented
Mar 20, 2026
src/routes/blog/post/build-internal-tools-quickly/+page.markdoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
src/routes/blog/post/when-custom-backend-stops-being-worth-it/+page.markdoc
Outdated
Show resolved
Hide resolved
adityaoberai
commented
Mar 20, 2026
src/routes/blog/post/firebase-vs-open-source-tradeoffs/+page.markdoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com> Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
adityaoberai
commented
Mar 20, 2026
…bsite into add-new-blogs-aditya
atharvadeosthale
approved these changes
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)
Summary by CodeRabbit