Managed Package target config for the LWC - namespace not resolved #5775
az-oolloow
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Firstly, this may not even be SFDX issue per se, but i am not sure where else to raise it.
I am developing a managed package with a custom namespace.
Because of that, when i define e.g. a record page LWC, i need to qualify my object in the
targetConfig
in the LWC component metadata, e.g. like so:This is mighty annoying because this is literally the only place in the project where i HAVE to specify the namespace.
We have a couple of non-scratch environments, and i need to manually change these files each time i want to deploy to the other one, which gets somewhat annoying even with the powers of bash and awk.
Is there any way to have these resolved on deployment, e.g. the same way as the namespacing works in javascript and Apex files?
Beta Was this translation helpful? Give feedback.
All reactions