Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

For extension packages being developed alongside a base package, to support base API changes for the extension, the base is represented by a proxy package using a different namespace prefix so that the base can be updated incrementally during the development sprint. 


Some changes to a managed package are irrevocable, in particular global class interfaces consumed by extensions and integrations. By using a proxy base package under an alternate namespace, changes can be tested in a complete development environment. If necessary, the proxy package can be discarded, and another alternate namespace chosen.

  • No labels