Using custom parameters with the transformer right now is tedious, as you have to provide an absolute import path. As the global import doesn't exist anymore, it'd be nicer to just assume the parameter type is in scope. We also don't need to map names anymore as we're introducing the notion of pass-thru parameters (like Readonly<T>).
New parameter map can just be a Record<string, boolean>, where the key is the name of the type to recognize, and boolean is if we pass act on it (true for most, false for pass-thru).
This will significantly improve the ergonomics of custom system parameters with the transformer
Describe the problem this feature solves
Using custom parameters with the transformer right now is tedious, as you have to provide an absolute import path. As the global import doesn't exist anymore, it'd be nicer to just assume the parameter type is in scope. We also don't need to map names anymore as we're introducing the notion of pass-thru parameters (like
Readonly<T>
).New parameter map can just be a
Record<string, boolean>
, where the key is the name of the type to recognize, and boolean is if we pass act on it (true
for most,false
for pass-thru).This will significantly improve the ergonomics of custom system parameters with the transformer