feat: add rules.read and rules.write to API key scopes#2972
feat: add rules.read and rules.write to API key scopes#2972singhvishalkr wants to merge 2 commits into
Conversation
Greptile SummaryThis PR adds
Confidence Score: 5/5Safe to merge — the change is purely additive, exposes previously hidden but already-supported scopes, and does not alter any existing logic. Only two constant entries are added, both matching existing patterns exactly. The scopes were already accepted by the backend (present in defaultScopes); this change simply makes them visible in the UI. No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "Merge appwrite/console main into fix/add..." | Re-trigger Greptile |
|
Gentle nudge — this one's been sitting green for ~11 days with only bot review. It's a small, targeted addition of the two missing |
Resolve scopes table conflict: keep rules.read/rules.write alongside upstream executions.read rename.
|
Merged current \�ppwrite/console\ \main\ (**\ |
What does this PR do?
Adds the missing
rules.readandrules.writescope definitions to the API key scopes list insrc/lib/constants.ts.These scopes are already included in
defaultScopesbut were missing from the selectable scope definitions, making them invisible in the API key creation/editing UI.Closes #2156
Changes
rules.readandrules.writeentries to thescopesarray with appropriate descriptions, matching the style of existing scope definitions.How to test
rules.readandrules.writenow appear in the scopes list