Add settings preference client - #133
cb-hareeshv wants to merge 1 commit into
Conversation
Expose list and upsert for /preferences, plus preference definitions, including the billing_rules setting group. Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (9)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe SDK adds ChangesPreference resources
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Feature Merge Risk: ⚪ Minimal · up to The new preference clients have no established merge-blocking defect. Their endpoint response shapes and variant encoding remain unconfirmed. 🚥 Pre-merge checks | ❌ 1❌ Failed checks (1 warning)
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
Preference.list/Preference.upsertandPreferenceDefinition.list_definitions).billing_rulessetting group fromfeat/SSM-1125.Test plan
cb.Preference.list({"setting_group": {"is": "billing_rules"}})callsGET /preferencescb.Preference.upsert(...)callsPOST /preferencescb.PreferenceDefinition.list_definitions(...)callsGET /preferences/definitionsSettingGroup.BILLING_RULESis"billing_rules"Made with Cursor
Adds Python v3 clients for
PreferenceandPreferenceDefinition. The clients support listing and upserting preferences and listing definitions. Adds response models and theAccessMode,Operand, andSettingGroupenums, includingBILLING_RULES.