-
Notifications
You must be signed in to change notification settings - Fork 65
Consistent use of capilalizaiton in output #327
Copy link
Copy link
Open
Labels
breakingBreaking change (CLI, input & output files)Breaking change (CLI, input & output files)comp-DocsRelated to documentationRelated to documentationcomp-MiscRelated to tools in /miscRelated to tools in /misccomp-UIRelated to user interface (command line, input files)Related to user interface (command line, input files)pri-MediumWorth assigning to a milestoneWorth assigning to a milestone
Milestone
Description
Metadata
Metadata
Assignees
Labels
breakingBreaking change (CLI, input & output files)Breaking change (CLI, input & output files)comp-DocsRelated to documentationRelated to documentationcomp-MiscRelated to tools in /miscRelated to tools in /misccomp-UIRelated to user interface (command line, input files)Related to user interface (command line, input files)pri-MediumWorth assigning to a milestoneWorth assigning to a milestone
Type
Fields
Give feedbackNo fields configured for Task.
Currently, ADDA mostly capitalizes first letters in each new line (sentence) in the output (
logandstdout), but several lines start with small letters. The change itself is pretty straightforward, but this cause many warnings in tests that compare the output, so this better need to be done before the release. Some changes in the manual and wiki pages may also be needed.Also this may break backward compatibility for parsers, so at least the ones supplied with ADDA need to be updated (i.e.,
misc/parse_log).In principle, this applies to other output files as well, but we need to consider them separately, whether there is any clear inconsistency inside one file.