Class Mapping
Resolve Core and origin references to the alias-specific data classes.
Resolve both entry points
Check Core classes referenced directly by shared components and origin classes referenced by the reused application. The alias mapping must resolve both kinds of entry points to the correct concrete alias classes.
Avoid incomplete mappings
An apparently working page is not sufficient proof of data isolation. Test authentication, Core Apps, lists, document editors, REST and background processes, because each may reach different data classes.
Configuration and command examples
These examples are preserved from the alias pre-documentation. Review the active environment and application names before applying them.
'contexts' => [
'shared' => [
\Core\Collection\AdminUserCollection::class
=> \AppnetosAliasDnsControl\Core\Collection\AppnetosAliasDnsControlAdminUserCollection::class,
\AppnetosDnsControl\Core\Collection\AppnetosDnsControlAdminUserCollection::class
=> \AppnetosAliasDnsControl\Core\Collection\AppnetosAliasDnsControlAdminUserCollection::class,
\Core\Document\AdminUser::class
=> \AppnetosAliasDnsControl\Core\Document\AppnetosAliasDnsControlAdminUser::class,
\AppnetosDnsControl\Core\Document\AppnetosDnsControlAdminUser::class
=> \AppnetosAliasDnsControl\Core\Document\AppnetosAliasDnsControlAdminUser::class,
],
],
rg -n 'Collection::class|Document::class|Registry::get|Registry::getNew' appnetos-dns-control/shared appnetos-dns-control/admin appnetos-dns-control/cmd appnetos-dns-control/worker