refactor(ui): migrate console forms to react-hook-form (team#152) by luannmoreira · Pull Request #6619 · shellhub-io/shellhub

luannmoreira · 2026-07-07T18:32:23Z

Summary

Migrates every console drawer and page form to a single react-hook-form + Zod architecture (tracked in shellhub-io/team#152). All in-scope forms now share one validation, submit, reset, and error-handling model, and the legacy makeRhfResolver adapter is removed.

The pilot (SignUp) and the auth/onboarding forms were merged separately and are intentionally left on their existing resolvers (converted in a later PR).

Architecture — four layers

Field wrappers (components/common/fields/rhf/*) — thin useController bridges over the design-system inputs (FormInputField, FormPasswordField, FormNumericInput, FormCheckboxField, FormRadioGroupField, FormTextareaField, FormToggleField). FormToggleField now renders its validation error like the other fields and uses the design-system Toggle primitive.
Schema + business module — one colocated *Schema.ts per form as the single source of truth: a Zod schema (a schema(mode) factory where rules are mode-dependent), type X = z.infer<...>, buildXDefaults, and buildXBody. All business logic (trimming, parseInt, payload shaping, SAML cert normalization) lives here, not in components.
State + lifecycle — useDrawerForm(open, schema, defaults) wraps useForm({ resolver: zodResolver(schema), mode: "onChange" }) and standardizes reset-on-open. The resolver uses a ref-based wrapper to avoid the stale-resolver bug when the schema changes between renders.
UI plumbing — FormDrawer owns the Drawer, <form>, Cancel/Submit footer (disabled on !isValid || isSubmitting, optional requireDirty), and the shared FormRootError.

A new form = write xSchema.ts + a drawer that calls useDrawerForm and renders <FormDrawer> with field wrappers. No hand-rolled resolver, reset, submit, or root-error code.

Migrated forms

Account & settings: profile (edit-profile + change-password), namespace rename, SAML config.

Resources: firewall rule, public key, secure vault key.

Admin: create/edit user (bespoke useUserForm hook removed), edit namespace, announcements — new/edit (full-page forms using useForm + zodResolver directly, no FormDrawer).

Team: add/edit member, generate/edit API key.

Two dual-mode drawers (Add Member, Generate Key) swap to a result view after submit, so they compose useDrawerForm + field wrappers + FormRootError under a raw Drawer rather than FormDrawer.

Cleanup

Removed makeRhfResolver and its test, and the per-form resolver adapters — zodResolver(schema) inside useDrawerForm is now the only resolver.
Resolver unit tests converted to schema.safeParse tests with equivalent coverage.

Behavior change

FormDrawer gates the submit button on isValid, so an invalid form now keeps submit disabled rather than enabled-but-blocked-on-click. A few drawer/page assertions were updated accordingly (async enable via waitFor; the invitation email field flags itself invalid inline as typed).

Test plan

npm run build (tsc + vite) passes
npm run lint passes (0 errors)
Full vitest console suite passes (2835 tests)

github-actions · 2026-07-07T18:32:52Z

Claude finished @luannmoreira's task in 8m 26s —— View job

Code Review Complete

Reviewed 17 files across code quality, security, testing, language patterns, and architecture. 1 inline issue posted (1 medium).

Additional notes

EditProfileDrawer now validates all fields unconditionally (pages/Profile.tsx:302, pages/profile/editProfileResolver.ts). The old form only validated a field when it diverged from its saved value, so a stored value that fails the stricter client-side rules (e.g. a legacy mixed-case username failing validateUsername's lowercase rule) didn't block editing other fields. Now disabled={!isDirty || !isValid ...} gates Save on all fields passing, so such an account could be permanently blocked from saving any change. Not posted inline because the impact depends on whether the backend can actually produce values that fail these client regexes — worth confirming, and if possible, scoping resolver validation (or the isValid gate) to dirty fields to preserve the previous UX.

Otherwise the migration is solid: the resolver values: {}-on-error shape matches RHF's Resolver contract, FormTextareaField mirrors the existing rhf/ wrappers correctly, submit payloads (Profile, Settings, SAML both modes, ChangePassword) are preserved verbatim, no any introduced, no security-relevant sinks/secrets, and the new resolver + drawer tests assert real behavior. No cross-repo (cloud/) impact — the new files aren't consumed there.

If you've addressed the feedback and want a new review, tag @shellhub-io/admin and a team member can trigger it.

otavio · 2026-07-09T14:37:53Z

/review

github-actions · 2026-07-09T14:38:19Z

Claude finished @otavio's task in 19m 54s —— View job

Code Review Complete

Reviewed the current PR head (c9b603e, 19 commits) across code quality, security, testing, TypeScript/React patterns, and architecture/cross-repo. 3 inline issues posted (1 medium, 2 low).

⚠️ Note: the branch advanced well beyond the snapshot in the last automated review — it now completes the full migration (~70 files), switches resolvers to zod schemas (*Schema.ts), and centralizes the form-reset lifecycle in the new useDrawerForm hook. This review is against the current head. The previous review's reset()-on-prop-change concern (Profile/Settings/SAML/etc.) is resolved: useDrawerForm resets only on the closed→open transition via a wasOpen ref, so it no longer wipes in-progress edits.

Findings posted inline:

ruleSchema.ts:29-31 (medium) — priority validation loosened; the old form rejected priority <= 0 ("must be a positive integer"), the schema now accepts 0/negatives. The field hint still says "Must be greater than 0." and a new test locks in the "0" behavior.
RuleDrawer.test.tsx:143-169 (low/medium) — the test "keeps submit disabled when tags mode has more than 3 tags" selects only 3 tags and asserts the button is enabled, contradicting its title; the > 3 rejection branch has no drawer-level coverage (only unit coverage in ruleSchema.test.ts).
secure-vault/KeyDrawer.tsx:49 (low) — setValue("passphrase", "") omits { shouldValidate: true } (unlike every sibling call), leaving isValid/errors.passphrase stale when swapping encrypted keys.

Additional notes

Cross-repo: no impact — cloud/ is Go-only and consumes none of these files. The one modified shared component (RadioGroupField.tsx, +6) is purely additive (optional error prop; FieldError renders null when empty), so existing consumers are unaffected. New deps (@hookform/resolvers, zod) are consistent with the lockfile.
Security: no exploitable issues. Every zod schema was compared against the base validators — samlSchema, userSchema (blank-password-keeps-current preserved), keySchema/vaultKeySchema, team/profile/password schemas all faithfully reproduce prior validation and submit payloads; editProfileSchema still submits only dirty fields. Minor non-security note: buildRuleBody no longer .trim()s source_ip/username (cosmetic payload change).

If you've addressed the feedback and want a new review, tag @shellhub-io/admin and a team member can trigger it.

- Restore the positive-integer rule for firewall priority (reject 0 and negatives), matching the field hint and pre-migration behavior. - Validate on clearing the secure-vault passphrase so isValid/errors stay in sync when swapping in a different encrypted key. - Rework the firewall tags test to verify the 3-tag selector cap instead of passing on a valid 3-tag selection.

otavio · 2026-07-09T15:58:42Z

/review

github-actions · 2026-07-09T15:59:01Z

Claude finished @otavio's task in 12m 43s —— View job

Code Review Complete

Reviewed 69 files across code quality, security, testing, TypeScript/React patterns, and architecture/cross-repo — no new issues found. The code looks good as-is.

The four issues from the previous review rounds are all confirmed fixed in 797df19:

ruleSchema.ts — positive-integer priority rule restored (rejects 0/negatives).
secure-vault/KeyDrawer.tsx — setValue("passphrase", "", { shouldValidate: true }).
RuleDrawer.test.tsx — reworked to verify the 3-tag selector cap.
Profile/Settings reset-on-prop-change — resolved by useDrawerForm's wasOpen guard.

Spot-checks that came back clean: removed symbols (makeRhfResolver, useUserForm) have no remaining importers; RadioGroupField's new optional error prop is backward-compatible with all 8 existing consumers; no cloud/ cross-repo impact (Go-only); submit payloads (buildUserPayload, buildKeyBody, buildRuleBody, SAML both modes, invitations/keys) faithfully match the pre-migration shapes; no any introduced and no XSS/secret-handling regressions; the two dual-mode drawers (Invitation, GenerateKey) correctly reimplement the reset/submit lifecycle outside FormDrawer.

If you push additional changes and want a new review, tag @shellhub-io/admin and a team member can trigger it.

otavio · 2026-07-09T22:05:05Z

/review

github-actions · 2026-07-09T22:05:23Z

Claude finished @otavio's task in 6m 39s —— View job

Code Review Complete

Reviewed 69 files across code quality, security, testing, TypeScript/React patterns, and architecture/cross-repo — no new issues found. The code looks good as-is.

All four issues from previous review rounds remain resolved at the current head (3aafeb6):

ruleSchema.ts — positive-integer priority rule restored (rejects 0/negatives).
secure-vault/KeyDrawer.tsx — setValue("passphrase", "", { shouldValidate: true }).
RuleDrawer.test.tsx — reworked to verify the TagsSelector 3-tag cap (4th click ignored → 3 chips).
Profile/Settings reset-on-prop-change — guarded by useDrawerForm's wasOpen closed→open ref.

Spot-checks that came back clean:

Schemas faithfully port (or strengthen) prior validation — samlSchema, userSchema (blank-password-keeps-current preserved), keySchema (now adds 64-char max), ruleSchema (now adds isValidRegex on IP/username/hostname), vaultKeySchema, editProfileSchema/changePasswordSchema, team/schemas (roleField excludes owner), editNamespaceSchema/namespaceRenameSchema/announcementSchema. No loosened validation, no XSS/secret-handling regressions.
Removed symbols (makeRhfResolver, useUserForm) have zero remaining importers — no build break.
RadioGroupField's new optional error prop is backward-compatible with all existing consumers (FieldError renders null on empty).
Dual-mode drawers (InvitationDrawer, GenerateKeyDrawer) correctly reuse useDrawerForm + useResetOnOpen and match FormDrawer's submit gating.
No cloud/ cross-repo impact (Go-only, consumes none of these files); new deps (@hookform/resolvers, zod) are consistent across package.json and package-lock.json.
No any introduced, no leftover console.log/debugger/TODO; test titles match their assertions.

If you push additional changes and want a new review, tag @shellhub-io/admin and a team member can trigger it.
• refactor/adopt-react-hook-form

…rimitives Introduce the shared foundation for the console form standardization (shellhub-io/team#152): FormDrawer owns the Drawer, form element, and Cancel/Submit footer; useDrawerForm wraps useForm with zodResolver and reset-on-open; FormRootError renders form-level server errors; and the react-hook-form field wrappers (FormNumericInput, FormRadioGroupField, FormTagsSelector, FormTextareaField, FormToggleField) bridge useController over the design-system inputs. Adds the react-hook-form and zod dependencies.

otavio · 2026-07-14T15:39:53Z

/review

github-actions · 2026-07-14T15:40:13Z

Claude finished @otavio's task in 16m 4s —— View job

Code Review Complete

Reviewed 66 files across code quality, security, testing, TypeScript/React patterns, and architecture/cross-repo. 1 inline issue posted (1 low).

Profile.tsx:368 (low) — ChangePasswordDrawer.onValid never clearErrors("root") (unlike every sibling drawer), so a failed-then-successful submit briefly shows the red error and green success banner together. Confirmed regression from the pre-refactor unconditional setError("").

Additional notes

Otherwise the migration is clean at the current head:

Schemas faithfully port prior validation — samlSchema (cert/URL helpers byte-identical), userSchema (blank-password-keeps-current), keySchema/vaultKeySchema, ruleSchema (positive-integer priority + regex checks), team/profile/announcement/namespace schemas. No loosened validation, no XSS/secret regressions.
Submit payloads preserved — buildUserPayload, buildRuleBody, buildKeyBody (edit drops data), buildSamlBody (both modes), team/invitation/key bodies all match pre-migration shapes.
Removed symbols (useUserForm; makeRhfResolver already absent) have zero remaining importers; RadioGroupField's new optional error prop is backward-compatible with all existing consumers.
No cloud/ cross-repo impact (Go-only); new deps (@hookform/resolvers, zod) consistent between package.json and package-lock.json.
Tests assert real behavior; no title/assertion mismatches or flaky-by-construction cases. No any introduced.
The four issues from prior rounds (ruleSchema priority, secure-vault passphrase shouldValidate, RuleDrawer >3-tags test, Profile/Settings reset via useDrawerForm) all remain resolved.

If you've addressed the feedback and want a new review, tag @shellhub-io/admin and a team member can trigger it.
• refactor/adopt-react-hook-form

otavio · 2026-07-14T16:56:57Z

/review

github-actions · 2026-07-14T16:57:23Z

Claude finished @otavio's task in 8m 47s —— View job

Code Review Complete

Reviewed 66 files across code quality, security, testing, TypeScript/React patterns, and architecture/cross-repo. 1 inline issue posted (1 low).

profile/editProfileSchema.ts:16-24 (low) — editProfileSchema validates name/username/email unconditionally. The pre-refactor form only validated a field when it changed from its saved value (Profile.tsx@master:278-281), so a stored value failing today's stricter client rules didn't block editing other fields. Now FormDrawer's !isValid gate keeps Save disabled forever if any untouched field is legacy-invalid — realistically the "Deprecated"-badged Username (validateUsername rejects non-lowercase). This was raised as a non-inline note in the first review round and is still unaddressed.

Additional notes

Otherwise the migration remains clean at the current head:

Schemas faithfully port (or strengthen) prior validation — samlSchema (cert/URL helpers byte-identical), userSchema (blank-password-keeps-current, admin/confirmed flags), keySchema (adds 64-char max)/vaultKeySchema (passphrase validated locally, never persisted), ruleSchema (positive-integer priority + regex checks), team/announcement/namespace schemas. No loosened validation, no XSS/secret regressions.
Submit payloads preserved — buildUserPayload, buildRuleBody, buildKeyBody (edit drops data), buildSamlBody (both modes), buildEditNamespaceBody, team/invitation/key bodies all match pre-migration shapes.
Removed symbols (makeRhfResolver, useUserForm + its types) have zero remaining importers in ui/ and cloud/; RadioGroupField's new optional error prop is backward-compatible with all existing consumers.
No cloud/ cross-repo impact (Go-only, no .tsx); new deps (@hookform/resolvers@^3.10.0, zod@^3.25.76) consistent between package.json and package-lock.json.
Tests assert real behavior; the new *Schema.test.ts files reproduce equivalent-or-better coverage, and CreateUserDrawer.test.tsx was correctly flipped to toBeDisabled() to match the new schema-driven gating. No any introduced.
The five issues from prior rounds (ruleSchema priority, secure-vault passphrase shouldValidate, RuleDrawer >3-tags test, Profile/Settings reset via useDrawerForm, ChangePassword clearErrors("root")) all remain resolved.

If you've addressed the feedback and want a new review, tag @shellhub-io/admin and a team member can trigger it.
• refactor/adopt-react-hook-form

Migrate the edit-profile and change-password drawers to the shared react-hook-form + zod architecture (shellhub-io/team#152). Validation moves into editProfileSchema.ts and changePasswordSchema.ts as the single source of truth; required fields validate unconditionally and the recovery email stays optional with its cross-field rule re-running when the primary email changes. Form-level server errors use RHF root errors.

Migrate the Settings rename-namespace drawer to react-hook-form + zod (shellhub-io/team#152). The namespace-name rule lives in namespaceRenameSchema.ts and the rename error surfaces through an RHF root error. The session-recording and device-auto-accept toggles and the delete/leave dialogs are left as-is.

Migrate the admin SAML configuration drawer to react-hook-form + zod (shellhub-io/team#152). All business logic (certificate normalization, payload shaping) moves into samlSchema.ts, with the drawer reduced to field wrappers over the schema.

Migrate the firewall rule drawer to react-hook-form + zod (shellhub-io/team#152). ruleSchema.ts replaces the hand-rolled resolver as the single source of truth, and the drawer composes FormDrawer with the shared field wrappers.

Migrate the public key drawer to react-hook-form + zod (shellhub-io/team#152). keySchema.ts owns validation and payload shaping; the drawer composes FormDrawer with the shared field wrappers.

Migrate the secure vault key drawer to react-hook-form + zod (shellhub-io/team#152). vaultKeySchema.ts owns validation, and the drawer composes FormDrawer with the shared field wrappers.

Migrate the admin create/edit user drawers to react-hook-form + zod (shellhub-io/team#152). userSchema.ts becomes the single source of truth and the bespoke useUserForm hook is removed; the drawers compose FormDrawer with the shared field wrappers.

…m + zod Migrate the admin edit-namespace drawer to react-hook-form + zod (shellhub-io/team#152). editNamespaceSchema.ts owns validation; the drawer composes FormDrawer with the shared field wrappers.

…+ zod Migrate the New / Edit announcement full-page forms to react-hook-form + zod (shellhub-io/team#152). announcementSchema.ts owns validation; the pages use useForm with zodResolver directly rather than FormDrawer.

…+ zod Migrate the add-member and edit-member-role drawers to react-hook-form + zod (shellhub-io/team#152). The add-member and edit-role schemas live in team/schemas.ts, and constants.tsx gains FormRoleSelector — a react-hook-form binding over the shared RoleSelector used across the team drawers.

…-form + zod Migrate the generate-key and edit-key drawers to react-hook-form + zod (shellhub-io/team#152). The generate-key and edit-key schemas live in team/schemas.ts, including the string-bound expiry that is converted to the numeric API value in buildGenerateKeyBody. The generate-key drawer swaps to a result view after submit, so it composes useDrawerForm + field wrappers + FormRootError under a raw Drawer rather than FormDrawer.

otavio · 2026-07-14T18:18:48Z

/review

github-actions · 2026-07-14T18:19:05Z

Claude finished @otavio's task in 9m 9s —— View job

Code Review Complete

Reviewed 66 files across code quality, security, testing, TypeScript/React patterns, and architecture/cross-repo — no new issues found. The code looks good as-is.

All prior-round issues remain resolved at the current head (69657da):

ruleSchema.ts — positive-integer priority rule (rejects 0/negatives).
secure-vault/KeyDrawer.tsx — setValue("passphrase", "", { shouldValidate: true }).
RuleDrawer.test.tsx — verifies the TagsSelector 3-tag cap.
Profile/Settings reset-on-open — guarded by useDrawerForm's wasOpen closed→open ref.
ChangePasswordDrawer.onValid — now clearErrors("root") on every submit.
editProfileSchema — converted to a schema(current) factory that skips validation for unchanged fields, restoring the pre-migration "validate only when changed" behavior.

Spot-checks that came back clean:

Schemas faithfully port prior validation — userSchema (blank-password-keeps-current, admin/confirmed flags), samlSchema (cert/URL normalization byte-identical), keySchema/vaultKeySchema (passphrase used only to derive fingerprint/algorithm, never persisted), ruleSchema (regex + positive-integer priority), team/announcement/namespace/profile schemas. No loosened validation, no XSS/secret regressions.
Submit payloads preserved — buildUserPayload (incl. computeMaxNamespaces edit/create branching), buildRuleBody, buildKeyBody (edit drops data), buildSamlBody (both modes), buildEditNamespaceBody, team/invitation/key bodies all match pre-migration shapes.
Removed symbols (makeRhfResolver, useUserForm + its UserFormMode/UserFormValues types, now re-exported from userSchema.ts) have zero remaining importers in ui/ and cloud/; RadioGroupField's new optional error prop is purely additive and backward-compatible with all existing consumers.
No cloud/ cross-repo impact (Go-only, no .tsx); new deps (@hookform/resolvers@^3.10.0, zod@^3.25.76) consistent between package.json and package-lock.json.
Hooks & wrappers — useDrawerForm's ref-based resolver correctly tracks schema-identity changes without remounting; all rhf/ field wrappers bridge useController correctly; dual-mode drawers (AddMemberDrawer, GenerateKeyDrawer) reimplement the reset/submit lifecycle consistently. No any introduced.
Tests assert real behavior; the new *Schema.test.ts files reproduce equivalent-or-better coverage with no title/assertion mismatches.

If you push additional changes and want a new review, tag @shellhub-io/admin and a team member can trigger it.
• refactor/adopt-react-hook-form

luannmoreira requested a review from a team as a code owner July 7, 2026 18:32

luannmoreira mentioned this pull request Jul 7, 2026

refactor(ui): adopt react-hook-form for account & settings forms #6618

Closed

github-actions Bot reviewed Jul 7, 2026

View reviewed changes

Comment thread ui/apps/console/src/pages/Profile.tsx Outdated

luannmoreira self-assigned this Jul 7, 2026

luannmoreira added status/work-in-progress area/ui kind/refactor labels Jul 7, 2026

luannmoreira force-pushed the refactor/adopt-react-hook-form branch 2 times, most recently from 70c7ed4 to 443179b Compare July 8, 2026 19:49

github-actions Bot reviewed Jul 9, 2026

View reviewed changes

Comment thread ui/apps/console/src/pages/firewall-rules/__tests__/RuleDrawer.test.tsx Outdated

luannmoreira force-pushed the refactor/adopt-react-hook-form branch from c9b603e to 34f31d7 Compare July 9, 2026 14:51

github-actions Bot reviewed Jul 9, 2026

View reviewed changes

Comment thread ui/apps/console/src/pages/firewall-rules/ruleSchema.ts

github-actions Bot reviewed Jul 9, 2026

View reviewed changes

Comment thread ui/apps/console/src/pages/secure-vault/KeyDrawer.tsx Outdated

luannmoreira force-pushed the refactor/adopt-react-hook-form branch from 34f31d7 to 797df19 Compare July 9, 2026 15:17

luannmoreira added the do-not-merge label Jul 9, 2026

luannmoreira force-pushed the refactor/adopt-react-hook-form branch from 797df19 to 3aafeb6 Compare July 9, 2026 22:02

luannmoreira force-pushed the refactor/adopt-react-hook-form branch from 3aafeb6 to 5a16b59 Compare July 10, 2026 12:44

luizhf42 force-pushed the refactor/adopt-react-hook-form branch from 5a16b59 to da33d37 Compare July 14, 2026 12:19

luizhf42 force-pushed the refactor/adopt-react-hook-form branch from da33d37 to 9aef980 Compare July 14, 2026 15:30

github-actions Bot reviewed Jul 14, 2026

View reviewed changes

Comment thread ui/apps/console/src/pages/Profile.tsx

luizhf42 force-pushed the refactor/adopt-react-hook-form branch from 9aef980 to dcb6183 Compare July 14, 2026 16:47

github-actions Bot reviewed Jul 14, 2026

View reviewed changes

Comment thread ui/apps/console/src/pages/profile/editProfileSchema.ts Outdated

luannmoreira added 11 commits July 14, 2026 14:26

refactor(ui): migrate the public key form to react-hook-form + zod

8f96d0d

Migrate the public key drawer to react-hook-form + zod (shellhub-io/team#152). keySchema.ts owns validation and payload shaping; the drawer composes FormDrawer with the shared field wrappers.

refactor(ui): migrate the secure vault key form to react-hook-form + zod

4c1b7b7

Migrate the secure vault key drawer to react-hook-form + zod (shellhub-io/team#152). vaultKeySchema.ts owns validation, and the drawer composes FormDrawer with the shared field wrappers.

refactor(ui): migrate the admin edit-namespace form to react-hook-for…

e64c247

…m + zod Migrate the admin edit-namespace drawer to react-hook-form + zod (shellhub-io/team#152). editNamespaceSchema.ts owns validation; the drawer composes FormDrawer with the shared field wrappers.

luizhf42 force-pushed the refactor/adopt-react-hook-form branch from dcb6183 to 69657da Compare July 14, 2026 17:26

luizhf42 removed do-not-merge status/work-in-progress labels Jul 14, 2026

Uh oh!

Uh oh!

Conversation

luannmoreira commented Jul 7, 2026 • edited by luizhf42 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Architecture — four layers

Migrated forms

Cleanup

Behavior change

Test plan

Uh oh!

github-actions Bot commented Jul 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Additional notes

Uh oh!

Uh oh!

otavio commented Jul 9, 2026

Uh oh!

github-actions Bot commented Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Additional notes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

otavio commented Jul 9, 2026

Uh oh!

github-actions Bot commented Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Uh oh!

otavio commented Jul 9, 2026

Uh oh!

github-actions Bot commented Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Uh oh!

otavio commented Jul 14, 2026

Uh oh!

github-actions Bot commented Jul 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Additional notes

Uh oh!

Uh oh!

otavio commented Jul 14, 2026

Uh oh!

github-actions Bot commented Jul 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Additional notes

Uh oh!

Uh oh!

otavio commented Jul 14, 2026

Uh oh!

github-actions Bot commented Jul 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Complete

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

luannmoreira commented Jul 7, 2026 •

edited by luizhf42

Loading

github-actions Bot commented Jul 7, 2026 •

edited

Loading

github-actions Bot commented Jul 9, 2026 •

edited

Loading

github-actions Bot commented Jul 9, 2026 •

edited

Loading

github-actions Bot commented Jul 9, 2026 •

edited

Loading

github-actions Bot commented Jul 14, 2026 •

edited

Loading

github-actions Bot commented Jul 14, 2026 •

edited

Loading

github-actions Bot commented Jul 14, 2026 •

edited

Loading