https://sourceforge.net/p/wact/feature-requests/96/2005-02-19T04:05:11ZRecent changes to 96: compiler.ini - make tag paths mergeable2005-02-19T04:05:11Z2005-02-19T04:05:11ZMichael van Damhttps://sourceforge.net/u/mvandam/https://sourceforge.net2be3014ea5c9c0d26139fe0f4cfcf394e239ab41

<div class="markdown_content"><p>I've started using the 'merging' .ini file config<br /> handler lately. It works wonderfully for everything<br /> except one thing: in my compiler.ini I have to list<br /> all the WACT built-in tag paths in my [tags] section<br /> plus the paths containing my custom<br /> tags/filters/properties. I would prefer to only list<br /> my custom paths in the config file (and have the WACT<br /> ones automatically merged in).</p> <p>The merging config handler doesn't work as I'd like<br /> because the whole list of paths is stored as a single<br /> config value:</p> <p>[tags]<br /> path =<br /> "%WACT_TAG_ROOT%core;%WACT_TAG_ROOT%data;%WACT_TAG_ROOT%form;%WACT_TAG_ROOT%list;%WACT_TAG_ROOT%page;%WACT_TAG_ROOT%calendar;%WACT_TAG_ROOT%encode;%WACT_TAG_ROOT%html;%WACT_TAG_ROOT%front"</p> <p>That means if I have a 'tags.path' entry in my config<br /> file, it overwrites the one in the main WACT compiler.ini.</p> <p>What about the following minor change? You could<br /> instead list each path separately in the config file<br /> (like the classes in autoload.ini):</p> <p>[paths]<br /> core='%WACT_TAG_ROOT%core'<br /> data='%WACT_TAG_ROOT%data'<br /> form='%WACT_TAG_ROOT%form'<br /> ...</p> <p>Also the name [paths] is a more general description of<br /> the directories being pointed to. Currently they<br /> contain not only tags, but also filters and properties.</p> <p>The same comment could be made about any config values<br /> that store a list of elements. e.g.<br /> compiler.ini/parser.saxfilters</p> <p>What do you think?</p></div>