Skip to content

refactor(web): move limitsFormat into @t3tools/shared - #7420

Merged
maria-rcks merged 1 commit into
pingdotgg:t3code/usage-limits-analyticsfrom
derektrimm:fix/limits-format-shared
Aug 22, 2026
Merged

maria-rcks merged 1 commit into
pingdotgg:t3code/usage-limits-analyticsfrom
derektrimm:fix/limits-format-shared

refactor(web): move limitsFormat into @t3tools/shared

54e1cde
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Aug 18, 2026 in 1m 16s

Effect Service Conventions: No issues found

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.


🔍 Agent activity — reasoning, no tool calls

💭 Looking at this diff, I'm checking whether limitsFormat.ts is being moved from the web app to the shared packages directory, along with the corresponding package.json export updates and import paths. I need to verify if this is a pure utility function and whether any other parts of the codebase are still referencing the old location. I don't see a test file for limitsFormat in the web app, so let me check what existed at the merge base. Since this is just a pure helper function rather than an Effect service, there shouldn't be any import violations—named imports are fine for utility modules like this. The grep results at the merge base show the same behavior, so the tool might be resolving to head regardless. Since there's no old shim and no Effect service involved, this is a clean state. The check defaults to failure, but with no findings it should succeed—I'll format the response as JSON with "All clear" as the title and summary per the schema requirements.


Agent Credits: 20 credits