Expose naming convention logic
dror-weiss opened this issue · comments
Custom resources not used by SST need to be named, and we would like them to be normalized to SST convention.
Please expose the naming convention logic so that the library users can invoke for non-SST resources.
I would like to update that I have overridden the naming convention of SST by using '$transform' over Pulumi types, and this works better for me as it is normalized like everything else in my codebase: lowercase, dash separated, without type in name.
@thdxr, if you want you can close this issue.