Page 1 of 1

Unreachable Elements

Posted: Mon Mar 18, 2019 6:40 pm
by kirkilj
Is there a magical report that would scour a set of ditaval files and then march through all the files referenced from a root map and indicate if there are any filtering attribute values that are obsolete, meaning the removal of a value would not affect the filtering process based on the existing ditaval files. We'd like to move to a subjectscheme mechanism to control values of these select-atts, but we'd like to see if we'd break anything if we engage is a massive cleanup and mapping to new controlled values. It's a trip through history to see how some of these attributes were "stretched" to cover a wide set of use cases over the years.

Obviously, the include/exclude logic would need to be part of the evaluation.

It has some similarities to the goal of the static analysis of a programming language to identify unreachable code.


Re: Unreachable Elements

Posted: Tue Mar 19, 2019 8:53 am
by Radu
Hi John,

I'm afraid we do not have such a feature. I will add an internal issue with your use case and if we manage to implement something similar in a future version we'll let you know.