Add support for namespace restoration in single-org, multiple managed package configs

[Scott Wells]

Currently translation from development namespaces to official namespaces only works properly when there's a 1:1 correspondence. This is not the case when developing content for multiple managed packages in a single organization even though it will properly translate from official to development on deployment. To finish support for development of content for multiple managed packages in a single organization this is needed.

[Scott Wells]

Issue #528 was marked as a duplicate of this issue.

[Dmitry Omelchenko]

Voted, would be really nice to have this enhancement.

[Scott Wells]

I hate to say it but I just don't see this happening. It's a truly non-trivial problem to solve, especially with Lightning where you have required namespace references in JavaScript even in the same package source. Also, Packaging 2.0 should eliminate the need for this. There are also ways you can somewhat implement this yourself with retrieval substitution rules. I helped a user do just that earlier this week. Obviously that solution doesn't scale very well, but the amount of time required to get an implementation of this even close to right would be huge and I just don't see it as being broadly useful.

For those who are interested in this, I'd be curious to hear your thoughts on what I've said above.

[Scott Wells]

Removing version: Unassigned (automated comment)