fix(privacy): escape curly braces that break Astro build#28
Merged
Conversation
Astro treats {} as expression delimiters in template HTML. Replace
inline JSON snippets like {"consent": {"telemetry": false}} with
prose equivalents (set consent.telemetry to false in config.json)
to fix the build error: Expected "}" but found ":".
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
🚀 Preview deployed to Cloudflare Pages
|
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
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.
Problem
src/pages/privacy.astroused{"consent": {"telemetry": false}}inline in the HTML template body. Astro parses{as an expression delimiter, which caused a build failure:Fix
Replace the three inline JSON snippets with prose equivalents:
set consent.telemetry to false in ~/.pilot/config.jsonset consent.broadcasts to false in ~/.pilot/config.jsonset consent.reviews to false in ~/.pilot/config.jsonThe full JSON format is documented on the linked
/docs/consentpage.🤖 Generated with Claude Code