Enhancement Request
fdc3-standard contains a ContextType type and deprecated ContextTypes enum (composed from A StandaContextTypes and ExperimentalContextTypes enums) at https://github.com/finos/FDC3/blob/cdc754e507e81c0eb45cd47c59b11a949d77e8e3/packages/fdc3-standard/src/context/ContextType.ts
This is hand maintained and recently was found to out of sync with the contexts in the fdc3-contexts package (now fixed). The type and enum should move to the fdc3-context and be automatically maintained against the schemas (as we have the goal that adding a context is simple as adding the schema to fdc3-context) and moved to fdc3-context to facilitate that (export from there and re-export from fdc3-standard/fdc3 to avoid a breaking change).
A simple script couldextract the context types (standard and experimental) from the available schemas and populate the enum(s). The enum should be un-deprecated, as it is useful for developers and can be used to define the type (to avoid duplication):
export type ContextType= `${ContextTypes}`;
Enhancement Request
fdc3-standard contains a ContextType type and deprecated ContextTypes enum (composed from A StandaContextTypes and ExperimentalContextTypes enums) at https://github.com/finos/FDC3/blob/cdc754e507e81c0eb45cd47c59b11a949d77e8e3/packages/fdc3-standard/src/context/ContextType.ts
This is hand maintained and recently was found to out of sync with the contexts in the fdc3-contexts package (now fixed). The type and enum should move to the fdc3-context and be automatically maintained against the schemas (as we have the goal that adding a context is simple as adding the schema to fdc3-context) and moved to fdc3-context to facilitate that (export from there and re-export from fdc3-standard/fdc3 to avoid a breaking change).
A simple script couldextract the context types (standard and experimental) from the available schemas and populate the enum(s). The enum should be un-deprecated, as it is useful for developers and can be used to define the type (to avoid duplication):