fix: update tests for SchemaConfigFields and comingSoon logic

- registry.test: fallback now uses SchemaConfigFields, not ProcessConfigFields
- metadata.test: isEnabledAdapterType checks comingSoon first so
  intentionally withheld built-in adapters (process/http) stay disabled
This commit is contained in:
HenkDz 2026-04-01 23:23:14 +01:00
parent d7a7bda209
commit 388650afc7
2 changed files with 10 additions and 7 deletions

View file

@ -26,9 +26,11 @@ export function listKnownAdapterTypes(): string[] {
* Unknown types (external adapters) are always considered enabled.
*/
export function isEnabledAdapterType(type: string): boolean {
// Known external adapter — always valid
if (listUIAdapters().some((a) => a.type === type)) return true;
return !getAdapterDisplay(type).comingSoon;
// Check display registry first — built-in adapters like process/http are
// intentionally withheld even though they're registered as UI adapters.
if (getAdapterDisplay(type).comingSoon) return false;
// All other types (registered or external) are enabled.
return true;
}
/**
@ -37,8 +39,8 @@ export function isEnabledAdapterType(type: string): boolean {
* any non-"coming soon" adapter from the display registry.
*/
export function isValidAdapterType(type: string): boolean {
if (listUIAdapters().some((a) => a.type === type)) return true;
return !getAdapterDisplay(type).comingSoon;
if (getAdapterDisplay(type).comingSoon) return false;
return true;
}
/**