Some cq properties are stored under the conf nodes. For exmple, please, consider the following node http://localhost:4502/crx/de/index.jsp#/conf/node/sling%3Aconfigs/simpleConfig, in which some properties are stored e.g. cq:lastReplicated, cq:lastReplicatedBy, and cq:lastReplicationAction. These properties are displayed in the configuration page, which are irrelevant. In other words, they shouldn't be displayed at all. They are required for activation on node on publisher instance. I see under the config node some properties like jcr:mixinTypes,cq:ReplicationStatus, and jcrrimaryType which are not displayed. I assume there is some filter in which some properties are displayed which should not be displayed. If this is the case, then, it should be extended. For more explanation, please, see the attached screenshots.
yes, you're right. but the filtering logic is part of the sling implementation of context-aware configuration:
unfortunately it's currently hard-coded, but should be configurable so in AEM further properties could be included like the ones you discovered. i will think about a solution.
i've created https://issues.apache.org/jira/browse/SLING-6788 for a solution in sling itself. once implemented it has to be configured properly within AEM and then these properties should be hidden in the configuration editor automatically.
Thanks stefan for the quick reply and for creating a ticket on Sling. I hope it gets fixed soon.
should be fixed with deploying additional these bundles (not yet released):
with this you can configure to also filter out all properties starting with "cq:" namespace e.g.: