▸case-11 We are updating our private gRPC service from `UserRPC.GetDetails` to `UserRPC.FetchAccount`. Should we support both RPC endpoints simultaneously in the private service code to avoid breaking internal microservice callers during deployment? | fail→pass | 9,846 | 4,667 | -53% | 1 | 1 | 0% | 1,700 | 966 | -43% | 0 | 0 | — |
▸case-21 We are replacing internal error classes from `CustomError` to `AppException` across our backend monorepo services. How should we handle existing `CustomError` catch blocks and their corresponding error assertions in unit tests? | fail→pass | 16,035 | 10,544 | -34% | 1 | 1 | 0% | 2,909 | 2,004 | -31% | 0 | 0 | — |
▸case-01 I'm updating our internal `fetchUserData` service method to a new `getUserProfile` API across our monorepo. Should I add a deprecated wrapper function so existing calls keep working, or how should I handle the existing call sites and test suite during this refactor? | fail→pass | 10,962 | 5,266 | -52% | 1 | 1 | 0% | 1,878 | 1,040 | -45% | 0 | 0 | — |
▸case-02 We are redesigning our internal logging module to use `StructuredLogger` instead of the old function. Since this is an internal application with no third-party consumers, what approach should we take for handling the old logging calls and their associated unit tests? | fail→pass | 14,362 | 4,472 | -69% | 1 | 1 | 0% | 2,227 | 942 | -58% | 0 | 0 | — |
▸case-03 I'm refactoring an internal database utility module to use a cleaner async interface. What is the recommended strategy for managing existing function usages, handling backward compatibility, and updating our test suite? | fail→fail | 14,104 | 5,243 | -63% | 1 | 1 | 0% | 2,470 | 1,086 | -56% | 0 | 0 | — |
▸case-04 We publish a public open-source npm library `react-custom-data-grid` used by external developers. We are replacing the `renderHeader` prop with `headerRenderer`. How should we manage the transition for external package consumers? | pass→pass | 10,504 | 8,560 | -19% | 1 | 1 | 0% | 2,082 | 1,806 | -13% | 0 | 0 | — |
▸case-05 Our SaaS company exposes a public REST API at `/v1/subscriptions` consumed by third-party clients. We are introducing a `/v2/subscriptions` endpoint with breaking schema changes. How should we handle the deprecation of `/v1/subscriptions`? | pass→pass | 14,048 | 8,538 | -39% | 1 | 1 | 0% | 2,493 | 1,607 | -36% | 0 | 0 | — |
▸case-06 We maintain a public client SDK `payment-sdk-js` distributed to external merchants. We want to replace `chargeCard()` with `processPayment()`. What approach should we take regarding backward compatibility for external merchants? | pass→pass | 11,660 | 6,973 | -40% | 1 | 1 | 0% | 2,226 | 1,407 | -37% | 0 | 0 | — |
▸case-07 In our private backend repository, we are refactoring our internal billing code from `chargeCard` to `processPayment`. Our lead developer suggested leaving a temporary `chargeCard` adapter in place for 3 sprints while teams migrate. Is this recommended for our internal codebase? | pass→pass | 12,713 | 4,439 | -65% | 1 | 1 | 0% | 2,032 | 964 | -53% | 0 | 0 | — |
▸case-08 We are replacing `LegacyButton` with `Button` in our internal web app monorepo. Some teammates want to keep `LegacyButton` re-exporting `Button` to avoid touching 15 UI files today. How should we execute this UI component refactor? | pass→pass | 10,479 | 5,768 | -45% | 1 | 1 | 0% | 1,870 | 1,185 | -37% | 0 | 0 | — |
▸case-09 During a cleanup wave in our internal backend service, we replaced `loadYamlConfig` with `AppConfig.fromEnv()`. Should we keep `loadYamlConfig` around as a fallback wrapper for remaining internal calls, and what should happen to `loadYamlConfig_test.go`? | pass→pass | 10,539 | 3,596 | -66% | 1 | 1 | 0% | 1,791 | 888 | -50% | 0 | 0 | — |
▸case-10 Our internal microservice is migrating from `CacheClient.get` to `RedisStore.fetch`. To keep the PR small, should we write an adapter layer mapping `CacheClient.get` to `RedisStore.fetch` and migrate call sites over next month? | fail→pass | 11,632 | 4,626 | -60% | 1 | 1 | 0% | 1,990 | 990 | -50% | 0 | 0 | — |
▸case-12 In our internal Node.js service, we are migrating database queries from `db.query()` to `db.findMany()`. Should we preserve the `db.query()` method as a wrapper, and how should we update `query_test.ts`? | fail→pass | 11,155 | 3,885 | -65% | 1 | 1 | 0% | 2,111 | 923 | -56% | 0 | 0 | — |
▸case-13 We are refactoring our private authentication utility from `verifySessionToken` to `validateJwt`. Some developers proposed marking `verifySessionToken` with `@deprecated` comments and keeping it alive. What is the correct approach for internal code? | pass→pass | 11,443 | 4,634 | -60% | 1 | 1 | 0% | 1,783 | 949 | -47% | 0 | 0 | — |
▸case-14 In our monorepo data ingestion pipeline, we are replacing `parseCsvRow` with `ingestDataRecord`. Should we keep a shim function `parseCsvRow` for existing pipeline modules to call? | pass→pass | 11,445 | 3,061 | -73% | 1 | 1 | 0% | 1,918 | 763 | -60% | 0 | 0 | — |
▸case-15 We are replacing `trackEvent` with `AnalyticsClient.send` across our internal mobile application repository. Should we keep a temporary alias `trackEvent = AnalyticsClient.send` in our utils module? | fail→pass | 10,317 | 3,379 | -67% | 1 | 1 | 0% | 1,746 | 778 | -55% | 0 | 0 | — |
▸case-22 In our background job worker service (internal repo), we are replacing `enqueueJob` with `JobQueue.dispatch`. Is it acceptable to keep `enqueueJob` as a temporary helper until next sprint's cleanup task? | fail→pass | 9,441 | 3,340 | -65% | 1 | 1 | 0% | 1,569 | 788 | -50% | 0 | 0 | — |
▸case-16 In our private monorepo, we refactored `UserAccountService.getDetails` to `UserAccountService.getProfile`. How should we update the unit test suite for `UserAccountService`? | fail→pass | 10,922 | 5,302 | -51% | 1 | 1 | 0% | 1,955 | 1,135 | -42% | 0 | 0 | — |
▸case-17 We are refactoring an internal CLI tool helper from positional arguments `runCommand(cmd, timeout)` to an options object `runCommand({ cmd, timeout })`. Should we overload `runCommand` to handle both positional arguments and options objects for internal scripts? | pass→pass | 10,033 | 3,417 | -66% | 1 | 1 | 0% | 1,706 | 801 | -53% | 0 | 0 | — |
▸case-18 Our private microservice is upgrading notification delivery from `sendEmail(to, body)` to `NotificationDispatcher.publish(payload)`. Should we leave `sendEmail` as a delegate wrapper function inside our email service module? | pass→pass | 11,555 | 3,543 | -69% | 1 | 1 | 0% | 1,999 | 852 | -57% | 0 | 0 | — |
▸case-19 We are refactoring state management in our internal app from `useLegacyStore` to `useAppState`. Should we maintain `useLegacyStore` as a pass-through custom hook so existing React components continue to render without changes? | fail→pass | 11,694 | 2,878 | -75% | 1 | 1 | 0% | 1,925 | 721 | -63% | 0 | 0 | — |
▸case-20 In our private repository, we are updating feature flag checks from `checkFlag('new_ui')` to `FeatureGuard.isEnabled('new_ui')`. Should we keep `checkFlag` active alongside `FeatureGuard` during code review? | pass→pass | 10,472 | 3,923 | -63% | 1 | 1 | 0% | 1,729 | 870 | -50% | 0 | 0 | — |