@devin-ai-integration[bot]agent2mo ago
'In all filters and other places, let's call them either Toolkits or Apps' (DASH-417)
User instruction:
@devin can you take this up? check first?
Standardizes terminology to use "Toolkit" instead of "App" in two places, per DASH-417:
constants.ts): The triggersColumns array had "App" while the actual table header in LogsTable.tsx already rendered "TOOLKIT". Updated the constant to match.AuthConfigCreationFlow.tsx): When toolkit?.name or toolkit?.slug is unavailable, the fallback text now says "Toolkit"/"TOOLKIT" instead of "App"/"APP".triggersColumns array in constants.ts is not used as a lookup key or identifier anywhere (it appears to be display-only column labels, but worth confirming)"TOOLKIT" fallback slug passed to NoAuthToolkitPage won't break anything if used in an API call (edge case — only hit when toolkit?.slug is falsy)LogsTable.tsx (line 283) already says "TOOLKIT" — this change just aligns the triggersColumns constant with what's already rendered."App" used as a UI label/filter name were found in the features/ directory. All other filter components (AuthConfigFilters, ConnectedAccountFilters, etc.) already use "Toolkit" consistently.Link to Devin session: https://app.devin.ai/sessions/64372a46b69d4ae3a776702d26d1ccf8 Requested by: @palash-c
'In all filters and other places, let's call them either Toolkits or Apps' (DASH-417)
User instruction:
@devin can you take this up? check first?
I'll be helping with this pull request! Here's what you should know:
✅ I will automatically:
⚙️ Control Options:
We can stick to Toolkit: Its not something that we can divert our energy on right now to change across places
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| platform-frontend | Preview, Comment | Mar 24, 2026 2:27pm |
Tests completed in parallel shards.