[
https://issues.apache.org/jira/browse/DAFFODIL-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169989#comment-17169989
]
Steve Lawrence commented on DAFFODIL-1200:
------------------------------------------
Another approach would be to add a tunable, something like
{{diagnosticPathWidth}}, that allows users to set a maximum number of
characters to display for diagnostic paths. Taking git as an example since i
know it does this somethimes (see {{git diff --stat}}), we can then truncate
the beginning of paths that exceed this width, e.g
{{.../daffodil/section06/namespaces.tdml}}. Presumably the important path
information is all at the end. For backwards compatibility, we could default to
-1/0/MaxInt to disable this, but since it's a tunable it's easy to configure
for users that don't want this behaior. And we could plan to change the default
to something more reasonable when we decide it's worth breaking backwards
compatibility.
> Really long path names in diagnostic messages make them hard to read
> --------------------------------------------------------------------
>
> Key: DAFFODIL-1200
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1200
> Project: Daffodil
> Issue Type: Bug
> Components: Diagnostics, Usability
> Affects Versions: s15
> Reporter: Mike Beckerle
> Priority: Minor
>
> Giant long file paths like
> file:/home/mbeckerle/dataiti/git/daffodil/eclipse-projects/target/test/edu/illinois/ncsa/daffodil/section06/namespaces.tdml
> These clutter the error messages, and all but the section06/namespaces.tdml
> are noise.
> Almost nothing can be viewed without scrolling the window/panel to the right
> so as to get past these giant paths. Or alternatively they wrap around line
> after line.
> Any given path being displayed can have whatever the longest prefix of it
> that matches a location on the classpath, that longest prefix can be removed
> without _much_ loss of information content.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
