Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.
Once credits are available, push a new commit or reopen this pull request to trigger a review.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6111e12562
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| return validate_modulr_core_registry_apex_name( | ||
| name, | ||
| field_label="organization_name", | ||
| invalid_code=ErrorCode.INVALID_NAME, |
There was a problem hiding this comment.
Delegating validate_modulr_org_domain to validate_modulr_core_registry_apex_name now allows single-label orgs (e.g. acme) in register_org, but handle_resolve_name still validates with validate_modulr_resolve_name, which requires domain.subdomain format. This creates a regression where a successfully registered org name cannot be resolved forward (resolve_name rejects it before lookup), breaking the advertised register_org → resolve_name flow for newly accepted names.
Useful? React with 👍 / 👎.
1 participant
No description provided.