alistanis
Feature request: more general approach to specify ignored fields
A more general approach to specifying ignored <types> and <fields> maybe useful.
Like:
<type_list1>:<field_list1>;<type_list2>:<field_list2>;...
Which would be something like:
<type1>,<type2>,...:<field1>,<field2>,...;<type3>,<type4>,...:<field3>,<field4>,...;...
Where <type_list>:<field_list> => ignore these fields in these types
Both <type> and <field> can be * to indicate all.
And allow multiple instances of --ignore so that people with large lists can split it across multiple lines.
Another useful mechanism may be to have the tool use tags that are meant for the tool itself. The tool would read directives for fields from its own tag, remove the tag, and replace it with generated tags.
Thanks for the suggestions! I'll take a look at implementing this tonight.
I added another suggestion.
Another useful mechanism may be to have the tool use tags that are meant for the tool itself. The tool would read directives for fields from its own tag, remove the tag, and replace it with generated tags.
On Thu, Jan 21, 2016 at 11:13 AM, Christopher Cooper < [email protected]> wrote:
Thanks for the suggestions! I'll take a look at implementing this tonight.
— Reply to this email directly or view it on GitHub https://github.com/Alistanis/st/issues/4#issuecomment-173620575.
That's a very interesting proposition and would allow for much more dynamic behavior. I like it!
This would be in addition to the mechanism of specifying ignore specs on the command line. I mean, after all, the big value of the tool is in not having to specify a whole bunch of tags. The tags mechanism would be for very specific overrides.
On Thu, Jan 21, 2016 at 11:32 AM, Christopher Cooper < [email protected]> wrote:
That's a very interesting proposition and would allow for much more dynamic behavior. I like it!
— Reply to this email directly or view it on GitHub https://github.com/Alistanis/st/issues/4#issuecomment-173626001.