feat: first-week friction improvements (#50–#58) - #66
Conversation
#56 #57 #58 - infra: dev.sh/dev.ps1 start all services with one command (#50) - backend: .golangci.yml + make lint target (#51) - mobile: Spotless/ktlint formatting enforcement + CI step (#52) - infra: renovate.json for automated dependency updates (#53) - infra: setup.sh/setup.ps1 first-run contributor script (#54) - backend: Swagger staleness check in backend-ci.yml (#55) - mobile: UiState<T> sealed class + UiStateContent composable (#56 #57) - mobile: HomeViewModel + HomeScreen refactored to UiState pattern (#56 #57) - web: DataTable component (TanStack Table v8, sort/filter/paginate) + /demo (#58) - docs: ui-states.md, data-table.md, updated CONTRIBUTING.md with prereqs and dev scripts
|
Warning Review limit reached
More reviews will be available in 20 minutes and 45 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (73)
✨ Finishing Touches🧪 Generate unit tests (beta)
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
dev.sh/dev.ps1— start Postgres, backend, and web with one commandbackend/.golangci.yml+make lint— golangci-lint v2 with practical rulesetspotlessCheckstep; reformats all Kotlin sources to consistent stylerenovate.json— minor/patch automerge, Monday schedule, grouped by layersetup.sh/setup.ps1— first-run script: checks prereqs, installs deps, copies.envfiles, runs migrationsbackend-ci.yml— fails PR if generated docs are out of dateUiState<T>sealed class +UiStateContentcomposable — generic loading/error/retry/success pattern;HomeScreenrefactored from rawLaunchedEffecttoHomeViewModel+UiStateDataTable<TData, TValue>— TanStack Table v8 with column sort, text filter, pagination;/demoroute; 91 Vitest testsmobile/docs/ui-states.md,web/docs/data-table.md, updatedCONTRIBUTING.md(prereqs, dev scripts, quality gate commands)Test plan
go vet ./...— cleanmake test— all pass (Postgres Testcontainers skip is pre-existing Windows Docker constraint)pnpm lint— 0 errors (1 warning onuseReactTable, known React Compiler compatibility note)pnpm build— clean,/demoroute included./gradlew lint— BUILD SUCCESSFUL./gradlew test— BUILD SUCCESSFUL./gradlew connectedAndroidTest— requires emulator (excluded from standard gate)