connection-form.tsx uses removed Modal contentClassName; forces dual compass-components versions

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • None
    • Developer Tools

      Extension main relies on pnpm resolving two @mongodb-js/compass-components versions at once:

      • own connection-form.tsx1.59.2 (Modal still accepts contentClassName, removed in 1.61.0)
      • connection-form@1.84.11.67.1 (needs useSyncStateOnPropChange, added in 1.60.0)

      Extension CI is green, but any consumer that dedupes to one version breaks — e.g. mongosh's test_vscode (overrides compass-components to a single copy):

      • <1.60useSyncStateOnPropChange is not a function
      • >=1.61Modal contentClassName TS2322

      Introduced by VSCODE-787 (#1318). Fix: drop deprecated contentClassName, bump direct compass-components to match connection-form. Discuss in triage.

            Assignee:
            Unassigned
            Reporter:
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: