Repository navigation
feat(frontier): add blockers to OrganizationToLeave - #504
Conversation
CheckCurrentUserDelete can now say why the user cannot leave an organization yet, such as being its only owner while other members remain. The top-level blockers list stays for reasons that do not belong to one organization.
|
The latest Buf updates on your PR. Results from workflow Validate / validate (pull_request).
|
|
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title names the main change: a new blockers field on the OrganizationToLeave message in the Frontier API. The raw summary confirms that exact change: a repeated Blocker blockers field at number 5.… |
| Description check | |
The description states that OrganizationToLeave gains blockers and explains its purpose. It gives the SOLE_OWNER_WITH_MEMBERS example and notes that the top-level blockers field remains. It also state… |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Title check
-
Explanation
The title names the main change: a new blockers field on the OrganizationToLeave message in the Frontier API. The raw summary confirms that exact change: a repeated Blocker blockers field at number 5. The title's scope is accurate and specific.
Full details: Description check
-
Explanation
The description states that OrganizationToLeave gains blockers and explains its purpose. It gives the SOLE_OWNER_WITH_MEMBERS example and notes that the top-level blockers field remains. It also states the change is non-breaking. This matches the raw summary and the PR objectives.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Some tools did not complete. Review the errors below.
🔧 Buf (1.73.0)
-
raystack/frontier/v1beta1/frontier.proto
-
fatal: unable to access 'https://github.com/raystack/proton.git/': Failed to connect to github.com:443 over proxy 127.0.0.1 after 0 ms: Could not connect to server
fatal: could not fetch fb5832b01e6503fe70d0a16bf0433e85917507ca from promisor remoteCODERABBIT_BUF_COMPATIBILITY_PHASE=materialize-base
-
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 @coderabbitai help to get the list of available commands.
Pins PROTON_COMMIT to 4e9e25ed, the commit in raystack/proton#504, which adds blockers to CheckCurrentUserDeleteResponse.OrganizationToLeave.
Pins PROTON_COMMIT to 4e9e25ed, the commit in raystack/proton#504, which adds blockers to CheckCurrentUserDeleteResponse.OrganizationToLeave.
CheckCurrentUserDeleteResponse.OrganizationToLeavegainsblockers. The check uses it to say why the user cannot leave that organization yet. For example,SOLE_OWNER_WITH_MEMBERSmeans the user is the organization's only owner and other members remain.The top-level
blockersfield stays, for reasons that do not belong to one organization.Adding a field is not a breaking change, so existing clients keep working.