Skip to content

Commit 46d7e83

Browse files
github-actions[bot]Marfuenclaude
authored
fix(treatment-plan): cap linked-work lists and treatment plan body height
* fix(treatment-plan): cap linked-work lists and treatment plan body height Long Tasks/Controls lists or AI-generated treatment plans were stretching the right (Linked Work) and middle (Treatment plan) columns past the Strategy column, leaving the row visually unbalanced and forcing the whole page to scroll just to see the bottom controls. - LinkedWork: each list (Tasks, Controls) now caps at max-h-80 with internal overflow-y-auto. The progress bar / counts stay pinned. - DescriptionEditor: markdown preview and the auto-growing textarea share a TEXTAREA_MAX_PX (480) cap. Past the cap, internal scroll takes over instead of pushing the row down. Net effect: the three columns stay roughly aligned regardless of how many tasks/controls are linked or how long the AI's plan runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(treatment-plan): paginate linked tasks and controls (4 per page) + seed fix LinkedWork - Each list (Tasks, Controls) now paginates at 4 items per page with prev/next + "X–Y of N" controls. Replaces the prior height cap + internal scroll. Long linked sets stay visually compact and the Linked Work column no longer pushes past the Strategy / Treatment plan columns regardless of list size. - Pagination state resets defensively when the underlying list shrinks past the current page (e.g. after an unlink). Seed fix (FrameworkEditorControlTemplate.json) - `documentTypes: null` → `documentTypes: []` for all 204 rows. The schema requires a non-nullable `EvidenceFormType[]` (default `[]`) but the export was writing nulls, which Prisma rejects on upsert. - Mapped enum values from kebab-case (`"infrastructure-inventory"`) to the TS-side snake_case (`"infrastructure_inventory"`). Prisma's client expects the enum identifier, not the `@map`'d DB string. Together these unblock `bun run db:seed` from a clean DB. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(seed): refresh framework editor templates + finding templates Updates the seed JSON exports to the latest snapshot. Touches: - FindingTemplate: regenerated with current cuid-style ids and the current title/content set the audit team is using. - FrameworkEditorFramework / PolicyTemplate / Requirement / TaskTemplate: refreshed primitives to match the live framework editor state. - Three Control↔(Task|Policy|Requirement) join files: refreshed to match the new template ids. bun.lock: dedup of @jridgewell/trace-mapping pulled in by `bun install`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(treatment-plan): hide linked work for non-mitigate + drop Avoid as a new selection Reverts two changes I introduced for Cubic findings #36 / #37 — they were technically correct readings of "ENG-221 keeps controls/tasks visible" but the user-intent was the opposite: Linked Work and the Avoid strategy are Mitigate-shaped concerns and shouldn't surface for treatments that aren't operational reductions. - TreatmentPlanTab: `showLinkedWorkColumn` is gated on `isMitigate && hasLinkedWork` again. Accept ("live with the risk"), Transfer (insurance / contractual instruments), and Avoid (discontinue the activity) are not control-driven mitigations, so the column adds noise and a misread when shown. - StrategyPicker: Avoid is back to legacy-only — never offered as a new selection, but rendered for risks that are already set to Avoid so existing state isn't dropped silently. - ScoreExplainer: dropped the Avoid bullet and the Avoid mention in the coverage-gate paragraph, matching what the picker now offers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(treatment-plan): url tabs, regen refresh, scroll caps, 4-per-page UX fixes layered into a single commit so they ship together. - RiskPageClient + VendorDetailTabs: active tab is now URL-backed via useQueryState('tab'), and only the active panel is mounted. This bookmarks the current tab in `?tab=...` (refresh keeps the view) and eliminates the visible "both panels stacked" flash on switch (base-ui keeps the outgoing panel at full opacity for the duration of the incoming `fade-in-0 duration-200` animation). - TreatmentPlanTab: drop the AutoMitigationPlaceholder ("AI is preparing your treatment plan…"). Its heuristic stayed true forever whenever the AI mitigation never wrote a description, so users sat on an indefinite spinner. Falling through to DescriptionEditor gives them the explicit "Generate treatment plan" button. - DescriptionEditor: regen-completion now bypasses the in-edit draft-resync guard. When the user clicks "Regenerate with AI" while in edit mode, they're explicitly opting into an overwrite, but the existing guard kept the textarea showing the old draft until refresh. Tracking regenRun's prev state and forcing preview + setDraft(value) on transition fixes it. - ScoreExplainer: cap the popover body at max-h-[70vh] with overflow-y-auto. The narrative + formulas + references could exceed the viewport on shorter screens with no way to reach the bottom. - AutoLinkSuggestions.sections: PAGE_SIZE 10 → 4 to match the new LinkedWork pagination. Selection UI now feels consistent with the post-apply view. - LinkedWork: explicit list-none + pl-0 on the Tasks/Controls `<ul>` to defeat an inherited list-style coming from somewhere (random bullet + ~40px left padding on each row). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(treatment-plan): drop orphan dot + checkbox-spacer indent on control rows Two visual bugs in the Controls list of AutoLinkSuggestions: - When `c.code` is empty (some frameworks ship controls without a code, e.g. "PCI"), the row rendered "· PCI" because the prefix format was unconditional `${c.code} · ${c.name}`. Now we only prepend the "code · " segment when a code exists. - Each row had a 16x16 invisible spacer <span> meant to align the control text with the task text below the task-row checkbox. In practice it just pushed controls ~24px to the right (spacer + gap), making them look indented relative to the section header and the Tasks rows above. Dropped the spacer so controls now align to the left edge of the column. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(onboarding): calibrate vendor inherent-risk prompt so well-known SaaS isn't 10/10 The previous system prompt for the AI vendor extraction had zero calibration guidance — just "return inherent_probability and inherent_impact". Without a rubric, gpt-4.1-mini defaulted every vendor to (very_likely × severe) = 25 → 10/10 CRITICAL. GitHub landed at 10/10 even though the same vendor card shows it carries SOC 2 + ISO 27001 + ISO 42001 + four other certifications. Adds explicit calibration: - Per-bucket definitions for inherent_probability (very_unlikely through very_likely), each anchored to concrete vendor archetypes (hyperscaler / SaaS-with-SOC-2 / no-attestation / etc). - Per-bucket definitions for inherent_impact, anchored to data classes (none / metadata / PII / auth-or-source-or-payments / production-infrastructure). - Explicit DEFAULT for residual: "leave residual = inherent unless the user's answers describe their OWN compensating controls." The vendor's certifications already feed into inherent — they shouldn't be double-counted as residual reductions. - Sanity-check sentence naming the well-known vendors that should land at (unlikely, moderate) ≈ 3/10, not 10/10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * refactor(onboarding): score vendor inherent risk from user signals, not name lookups Drop the hardcoded list of "well-known SaaS" vendor names from the inherent-risk calibration prompt. Maintaining a list inside an LLM prompt is brittle (every new well-known vendor is a prompt edit) and asks the LLM to reason from its prior knowledge rather than from the data we actually have. The new prompt makes two things explicit: 1. The model is scoring from the USER'S answers only — it does NOT have access to the vendor's public posture (SOC 2, ISO 27001, incident history). A separate research step (research-vendor → GlobalVendors) fills that in later, and a follow-up will use the researched data to refine the per-org Vendor row's score. 2. Default to MIDDLE (possible × moderate ≈ 5/10) when no signal exists. Only deviate when the user's answers contain explicit signals — listed by category (lowers probability / raises probability / lowers impact / raises impact). When the user simply NAMES the vendor with no further context, return (possible, moderate) and let the research step refine. This fixes the "GitHub got 10/10" pathology without coupling the prompt to a vendor name registry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Mariano <marfuen98@gmail.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 3c96a1d commit 46d7e83

19 files changed

Lines changed: 12787 additions & 1663 deletions

‎apps/app/src/app/(app)/[orgId]/risk/[riskId]/components/RiskPageClient.tsx‎

Lines changed: 91 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ import {
2424
Text,
2525
} from '@trycompai/design-system';
2626
import Link from 'next/link';
27-
import { useSearchParams } from 'next/navigation';
27+
import { useQueryState } from 'nuqs';
2828
import { useCallback, useMemo, useState } from 'react';
2929
import { toast } from 'sonner';
3030

@@ -71,8 +71,16 @@ export function RiskPageClient({
7171
discardRiskAutoLinkRun,
7272
} = useRiskActions();
7373
const { hasPermission } = usePermissions();
74-
const searchParams = useSearchParams();
75-
const defaultTab = searchParams.get('tab') || 'overview';
74+
// URL-backed tab state — bookmarks the active tab in `?tab=...` so a
75+
// refresh keeps the same view. Control the value so we can conditionally
76+
// render only the active panel below: base-ui's Tabs.Panel keeps the
77+
// outgoing panel mounted at full opacity for the duration of the
78+
// incoming panel's `fade-in-0 duration-200` animation, which produces
79+
// a visible "both panels stacked" flash. Mounting only the active panel
80+
// sidesteps the transition window entirely.
81+
const [activeTab, setActiveTab] = useQueryState('tab', {
82+
defaultValue: 'overview',
83+
});
7684
const isViewingTask = Boolean(taskItemId);
7785
const canUpdate = hasPermission('risk', 'update');
7886
const canUpdateTask = hasPermission('task', 'update');
@@ -307,7 +315,7 @@ export function RiskPageClient({
307315
{isViewingTask ? (
308316
<TaskItems entityId={riskId} entityType="risk" />
309317
) : (
310-
<Tabs defaultValue={defaultTab}>
318+
<Tabs value={activeTab} onValueChange={(next) => void setActiveTab(String(next))}>
311319
<Stack gap="lg">
312320
<TabsList variant="underline">
313321
<TabsTrigger value="overview">Overview</TabsTrigger>
@@ -319,77 +327,91 @@ export function RiskPageClient({
319327
<TabsTrigger value="settings">Settings</TabsTrigger>
320328
</TabsList>
321329

322-
<TabsContent value="overview">
323-
<RiskOverview risk={risk} assignees={assignees} />
324-
</TabsContent>
330+
{activeTab === 'overview' && (
331+
<TabsContent value="overview">
332+
<RiskOverview risk={risk} assignees={assignees} />
333+
</TabsContent>
334+
)}
325335

326-
<TabsContent value="treatment-plan">
327-
<TreatmentPlanTab
328-
orgId={orgId}
329-
entity={{
330-
id: risk.id,
331-
inherentLikelihood: risk.likelihood,
332-
inherentImpact: risk.impact,
333-
residualLikelihood: risk.residualLikelihood,
334-
residualImpact: risk.residualImpact,
335-
treatmentStrategy: risk.treatmentStrategy,
336-
treatmentStrategyDescription: risk.treatmentStrategyDescription,
337-
strategyDescriptions:
338-
(swrRisk as { strategyDescriptions?: unknown } | undefined)
339-
?.strategyDescriptions as
340-
| Partial<Record<RiskTreatmentType, string>>
341-
| null
342-
| undefined ?? null,
343-
// Fall through to the server-rendered initial risk so the
344-
// Linked Work column doesn't blink empty between SSR and
345-
// the first SWR resolution. (Cubic finding #28.)
346-
tasks:
347-
swrRisk?.tasks ??
348-
(initialRisk as unknown as { tasks?: RiskLinkedTask[] })
349-
.tasks ??
350-
[],
351-
}}
352-
canUpdate={canUpdate}
353-
onUpdateStrategy={handleUpdateStrategy}
354-
onUpdateDescription={handleUpdateDescription}
355-
onRegenerate={handleRegenerateMitigation}
356-
regenerating={isRegenerating}
357-
onSuggest={handleSuggest}
358-
onApply={handleApply}
359-
// Gate the unlink affordance behind risk:update so the trash
360-
// button doesn't render for read-only users. The Next API
361-
// route enforces the same check server-side as defense in
362-
// depth. (Cubic finding on PR #2671.)
363-
onUnlinkTask={canUpdate ? handleUnlinkTask : undefined}
364-
onResumeAutoLink={handleResumeAutoLink}
365-
onDiscardAutoLinkRun={handleDiscardAutoLinkRun}
366-
regenRun={regenRun}
367-
onRegenSettled={handleRegenSettled}
368-
/>
369-
</TabsContent>
336+
{activeTab === 'treatment-plan' && (
337+
<TabsContent value="treatment-plan">
338+
<TreatmentPlanTab
339+
orgId={orgId}
340+
entity={{
341+
id: risk.id,
342+
inherentLikelihood: risk.likelihood,
343+
inherentImpact: risk.impact,
344+
residualLikelihood: risk.residualLikelihood,
345+
residualImpact: risk.residualImpact,
346+
treatmentStrategy: risk.treatmentStrategy,
347+
treatmentStrategyDescription: risk.treatmentStrategyDescription,
348+
strategyDescriptions:
349+
(swrRisk as { strategyDescriptions?: unknown } | undefined)
350+
?.strategyDescriptions as
351+
| Partial<Record<RiskTreatmentType, string>>
352+
| null
353+
| undefined ?? null,
354+
// Fall through to the server-rendered initial risk so the
355+
// Linked Work column doesn't blink empty between SSR and
356+
// the first SWR resolution. (Cubic finding #28.)
357+
tasks:
358+
swrRisk?.tasks ??
359+
(initialRisk as unknown as { tasks?: RiskLinkedTask[] })
360+
.tasks ??
361+
[],
362+
}}
363+
canUpdate={canUpdate}
364+
onUpdateStrategy={handleUpdateStrategy}
365+
onUpdateDescription={handleUpdateDescription}
366+
onRegenerate={handleRegenerateMitigation}
367+
regenerating={isRegenerating}
368+
onSuggest={handleSuggest}
369+
onApply={handleApply}
370+
// Gate the unlink affordance behind risk:update so the trash
371+
// button doesn't render for read-only users. The Next API
372+
// route enforces the same check server-side as defense in
373+
// depth. (Cubic finding on PR #2671.)
374+
onUnlinkTask={canUpdate ? handleUnlinkTask : undefined}
375+
onResumeAutoLink={handleResumeAutoLink}
376+
onDiscardAutoLinkRun={handleDiscardAutoLinkRun}
377+
regenRun={regenRun}
378+
onRegenSettled={handleRegenSettled}
379+
/>
380+
</TabsContent>
381+
)}
370382

371-
<TabsContent value="risk-matrix">
372-
<Stack gap="lg">
373-
<InherentRiskChart risk={risk} />
374-
<ResidualRiskChart risk={risk} />
375-
</Stack>
376-
</TabsContent>
383+
{activeTab === 'risk-matrix' && (
384+
<TabsContent value="risk-matrix">
385+
<Stack gap="lg">
386+
<InherentRiskChart risk={risk} />
387+
<ResidualRiskChart risk={risk} />
388+
</Stack>
389+
</TabsContent>
390+
)}
377391

378-
<TabsContent value="tasks">
379-
<TaskItems entityId={riskId} entityType="risk" />
380-
</TabsContent>
392+
{activeTab === 'tasks' && (
393+
<TabsContent value="tasks">
394+
<TaskItems entityId={riskId} entityType="risk" />
395+
</TabsContent>
396+
)}
381397

382-
<TabsContent value="comments">
383-
<Comments entityId={riskId} entityType={CommentEntityType.risk} organizationId={orgId} />
384-
</TabsContent>
398+
{activeTab === 'comments' && (
399+
<TabsContent value="comments">
400+
<Comments entityId={riskId} entityType={CommentEntityType.risk} organizationId={orgId} />
401+
</TabsContent>
402+
)}
385403

386-
<TabsContent value="activity">
387-
<RiskActivitySection riskId={riskId} taskItemIds={taskItemsData?.data?.data?.map((t) => t.id) || []} />
388-
</TabsContent>
404+
{activeTab === 'activity' && (
405+
<TabsContent value="activity">
406+
<RiskActivitySection riskId={riskId} taskItemIds={taskItemsData?.data?.data?.map((t) => t.id) || []} />
407+
</TabsContent>
408+
)}
389409

390-
<TabsContent value="settings">
391-
<Text size="sm" variant="muted">No settings yet.</Text>
392-
</TabsContent>
410+
{activeTab === 'settings' && (
411+
<TabsContent value="settings">
412+
<Text size="sm" variant="muted">No settings yet.</Text>
413+
</TabsContent>
414+
)}
393415
</Stack>
394416
</Tabs>
395417
)}

‎apps/app/src/app/(app)/[orgId]/vendors/[vendorId]/components/VendorDetailTabs.tsx‎

Lines changed: 43 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ import {
3636
} from '@trycompai/design-system';
3737
import Link from 'next/link';
3838
import { useSearchParams } from 'next/navigation';
39+
import { useQueryState } from 'nuqs';
3940
import { useCallback, useEffect, useMemo, useState } from 'react';
4041
import { toast } from 'sonner';
4142

@@ -76,7 +77,6 @@ export function VendorDetailTabs({
7677
isViewingTask,
7778
}: VendorDetailTabsProps) {
7879
const searchParams = useSearchParams();
79-
const defaultTab = searchParams.get('tab') || 'overview';
8080
const taskItemId = searchParams.get('taskItemId');
8181

8282
const { vendor: swrVendor, mutate: refreshVendor } = useVendor(vendorId);
@@ -107,7 +107,14 @@ export function VendorDetailTabs({
107107
} | null>(null);
108108
const [isAssessmentLoading, setIsAssessmentLoading] = useState(false);
109109
const [isRegenerating, setIsRegenerating] = useState(false);
110-
const [activeTab, setActiveTab] = useState(defaultTab);
110+
// URL-backed tab state — bookmarks the active tab in `?tab=...` so a
111+
// refresh keeps the same view. Conditional rendering below mounts only
112+
// the active panel, sidestepping base-ui's transition window where the
113+
// outgoing panel stays at full opacity during the incoming fade-in
114+
// (visible "both panels stacked" flash on tab switch).
115+
const [activeTab, setActiveTab] = useQueryState('tab', {
116+
defaultValue: 'overview',
117+
});
111118

112119
const { data: taskItemsData, mutate: refreshTaskItems } = useTaskItems(
113120
vendorId, 'vendor', 1, 50, 'createdAt', 'desc', {},
@@ -338,7 +345,7 @@ export function VendorDetailTabs({
338345
toast.success('Assessment regeneration triggered.');
339346
if (result.runId && result.publicAccessToken) {
340347
setIsRegenerating(true);
341-
setActiveTab('risk-assessment');
348+
void setActiveTab('risk-assessment');
342349
handleAssessmentTriggered(result.runId, result.publicAccessToken);
343350
}
344351
refreshVendor();
@@ -472,7 +479,7 @@ export function VendorDetailTabs({
472479
{isViewingTask ? (
473480
<TaskItems entityId={vendorId} entityType="vendor" />
474481
) : (
475-
<Tabs value={activeTab} onValueChange={setActiveTab}>
482+
<Tabs value={activeTab} onValueChange={(next) => void setActiveTab(String(next))}>
476483
<Stack gap="lg">
477484
<TabsList variant="underline">
478485
<TabsTrigger value="overview">Overview</TabsTrigger>
@@ -485,10 +492,13 @@ export function VendorDetailTabs({
485492
<TabsTrigger value="settings">Settings</TabsTrigger>
486493
</TabsList>
487494

488-
<TabsContent value="overview">
489-
<SecondaryFields vendor={resolvedVendor} assignees={assignees} onUpdate={refreshVendor} />
490-
</TabsContent>
495+
{activeTab === 'overview' && (
496+
<TabsContent value="overview">
497+
<SecondaryFields vendor={resolvedVendor} assignees={assignees} onUpdate={refreshVendor} />
498+
</TabsContent>
499+
)}
491500

501+
{activeTab === 'treatment-plan' && (
492502
<TabsContent value="treatment-plan">
493503
<TreatmentPlanTab
494504
orgId={orgId}
@@ -525,14 +535,18 @@ export function VendorDetailTabs({
525535
onRegenSettled={handleRegenSettled}
526536
/>
527537
</TabsContent>
538+
)}
528539

540+
{activeTab === 'risk-matrix' && (
529541
<TabsContent value="risk-matrix">
530542
<Stack gap="lg">
531543
<VendorInherentRiskChart vendor={resolvedVendor} />
532544
<VendorResidualRiskChart vendor={resolvedVendor} />
533545
</Stack>
534546
</TabsContent>
547+
)}
535548

549+
{activeTab === 'risk-assessment' && (
536550
<TabsContent value="risk-assessment">
537551
<Stack gap="md">
538552
<AnimatePresence mode="wait">
@@ -580,19 +594,27 @@ export function VendorDetailTabs({
580594
</AnimatePresence>
581595
</Stack>
582596
</TabsContent>
583-
584-
<TabsContent value="tasks">
585-
<TaskItems entityId={vendorId} entityType="vendor" />
586-
</TabsContent>
587-
588-
<TabsContent value="comments">
589-
<Comments entityId={vendorId} entityType={CommentEntityType.vendor} organizationId={orgId} />
590-
</TabsContent>
591-
592-
<TabsContent value="activity">
593-
<VendorActivitySection vendorId={vendorId} taskItemIds={taskItemsData?.data?.data?.map((t) => t.id) || []} />
594-
</TabsContent>
595-
597+
)}
598+
599+
{activeTab === 'tasks' && (
600+
<TabsContent value="tasks">
601+
<TaskItems entityId={vendorId} entityType="vendor" />
602+
</TabsContent>
603+
)}
604+
605+
{activeTab === 'comments' && (
606+
<TabsContent value="comments">
607+
<Comments entityId={vendorId} entityType={CommentEntityType.vendor} organizationId={orgId} />
608+
</TabsContent>
609+
)}
610+
611+
{activeTab === 'activity' && (
612+
<TabsContent value="activity">
613+
<VendorActivitySection vendorId={vendorId} taskItemIds={taskItemsData?.data?.data?.map((t) => t.id) || []} />
614+
</TabsContent>
615+
)}
616+
617+
{activeTab === 'settings' && (
596618
<TabsContent value="settings">
597619
<Stack gap="lg">
598620
{canUpdate && (
@@ -616,6 +638,7 @@ export function VendorDetailTabs({
616638
)}
617639
</Stack>
618640
</TabsContent>
641+
)}
619642
</Stack>
620643
</Tabs>
621644
)}

‎apps/app/src/components/risks/treatment-plan/AutoLinkSuggestions.sections.tsx‎

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,9 @@ import {
1010
type SuggestedTask,
1111
} from './AutoLinkSuggestions.types';
1212

13-
const PAGE_SIZE = 10;
13+
// Match the LinkedWork list pagination so the selection UI feels consistent
14+
// with the post-apply view (also 4 per page).
15+
const PAGE_SIZE = 4;
1416

1517
function Pagination({
1618
page,
@@ -192,6 +194,11 @@ export function ControlsSection({
192194
<div className="mt-2">
193195
{visible.map((c) => {
194196
const isDerived = isControlDerived(c, checkedTaskIds);
197+
// Show "code · name" when the framework provides a code
198+
// (e.g. "1.2.7 · Credential Management"); fall back to just
199+
// the name when code is empty so we don't render a leading
200+
// "· " orphan separator.
201+
const heading = c.code ? `${c.code} · ${c.name}` : c.name;
195202
return (
196203
<div
197204
key={c.id}
@@ -200,11 +207,8 @@ export function ControlsSection({
200207
!isDerived && 'opacity-55',
201208
)}
202209
>
203-
<span className="mt-0.5 inline-block h-4 w-4 shrink-0" aria-hidden="true" />
204210
<div className="min-w-0 flex-1">
205-
<div className="text-[13px] leading-[1.4]">
206-
{c.code} · {c.name}
207-
</div>
211+
<div className="text-[13px] leading-[1.4]">{heading}</div>
208212
<div className="mt-0.5 text-[11px] leading-[1.4] text-muted-foreground">
209213
{c.framework}
210214
</div>

0 commit comments

Comments
 (0)