while investigating an issue involving sling:alias, i inadvertently created nested alias i.e. ended up having an alias define for the parent and a child page.
when looking at the values obtained from ResourceMapper.getAllMappings, i noticed that it only contains 1 combination. cross-checking however revealed that all combinations define valid paths that are properly resolved by sling.
parent: /parent with alias name 'alias-parent'
child: /parent/child with alias name 'alias-child'
valid paths for the child are (and expected from ResourceMapper.getAllMappings):
actual values obtained from ResourceMapper.getAllMappings:
consequently, an consumer of ResourceMapper.getAllMappings will miss valid alias path mappings. with additional nesting or addition of multiple alias values (see
SLING-9620), the number of missed paths will increase.