Namespace Mapping for Managed Packages
We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they are not.
All this means comparisons for managed package development are difficult and you must be very careful when deploying, which almost defeats the purpose of a tool like Gearset.
We really need some better management of namespaces, specifically for ISV partners, so that comparisons are better indicative of true changes between dev/test orgs and the namespaced package org.
We are also affected by this flaw in the comparsion process.This makes it difficult for our dev team to set up a seamless CI/CD pipeline for our managed apps and we are forced to go with workarounds.