enhancement: made setup process easier by including comments and vars… #234
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.
Hi, I have added some env variables and tested the template you gave, which required additional env vars so I added them and also updated defaultOptions in xata.js so that new commers can get idea about how to setup initially before making any changes to the codebase.
You can merge it if you want to .
Note
Simplifies local env setup by adding required vars/defaults, updates docs, ignores generated Xata files, and pins @xata.io/client to a specific prerelease.
/.env.example
with defaults forAUTH_SECRET
,AUTH_URL
, andXATA_BRANCH
.XATA_HTTP_ENDPOINT
and makeNEXT_PUBLIC_ANALYTICS_WEBSITE_ID
mandatory with a default UUID.CONTRIBUTING.md
env instructions.src/xata.js
,src/xata.ts
.@xata.io/client
to0.0.0-next.v93343b9646f57a1e5c51c35eccf0767c2bb80baa
.Written by Cursor Bugbot for commit a144d8f. This will update automatically on new commits. Configure here.