chore(docs): SDK page cleanup — sidebar, examples, tab naming, code structure#275
chore(docs): SDK page cleanup — sidebar, examples, tab naming, code structure#275marythought wants to merge 6 commits into
Conversation
Rearrange CreateTDF, LoadTDF, IsValidTdf, and BulkDecrypt sections so usage examples appear directly after the method signature, before the parameter tables. This makes it easier to see how to call each method without scrolling past reference details first. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Rearrange sidebar: Architecture → Authentication → Quickstart → TDF → Policy → Authorization → Discovery → Troubleshooting. Puts system understanding and auth setup before the quickstart and core operations. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
📄 Preview deployed to https://opentdf-docs-pr-275.surge.sh |
There was a problem hiding this comment.
Code Review
This pull request refactors the docs/sdks/tdf.mdx documentation by reordering sections for the createTDF, LoadTDF, IsValidTdf, and BulkDecrypt functions. Technical details including parameters, return types, and error descriptions have been moved to follow the code examples to improve readability and flow. I have no feedback to provide as there were no review comments to evaluate.
Some tabs used "TypeScript" or "Javascript" (lowercase s) while the majority used "JavaScript". Standardize all to "JavaScript" for consistency across SDK pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…age (#274) - Add Setup section to Policy page with client init for Go, Java, JS - Strip SDK initialization boilerplate from all inline code examples and imported code sample files — snippets now assume the shared setup - Extract Obligations into its own page (different service accessor) with its own Setup section (Go + JS only, no Java support yet) - Bump sidebar positions: Obligations=6, Authorization=7, Discovery=8, Troubleshooting=10 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Aligns with the Setup section naming used on the Policy and Obligations pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details. Once the build passes, the preview will be at: https://opentdf-docs-pr-275.surge.sh Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result: |
Show base imports for Go, Java, and JS so readers know where `sdk`, `SDKBuilder`, and `AuthProviders` come from before hitting the first code example. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Superseded by a fresh PR rebased on main after #270 merged. |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 49 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (18)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary
Addresses all 4 tasks from #274:
Closes #274
Test plan
🤖 Generated with Claude Code