Proposal to Add Optional Argument to `Schema.Literal` for Broader `I` Type Parameter

Do you think it makes sense to add an optional last argument to

Schema.Literal

Schema.Literal

(e.g.

{ encoded: 'broad' }

{ encoded: 'broad' }

) that would force the

type parameter to be broader than it currently is (i.e., not a type literal, but its supertype)? This could help solve cases like help-forumHttpApiSchema.param AnyString type-error.

Proposal to Add Optional Argument to `Schema.Literal` for Broader `I` Type Parameter - Effect Community