[jira] [Assigned] (DAFFODIL-2234) CLI needs to pass options to infoset inputters/outputters

["John Interrante (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Interrante reassigned DAFFODIL-2234:
-----------------------------------------

    Assignee: John Interrante

> CLI needs to pass options to infoset inputters/outputters
> ---------------------------------------------------------
>
>                 Key: DAFFODIL-2234
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2234
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 2.4.0
>            Reporter: Mike Beckerle
>            Assignee: John Interrante
>            Priority: Minor
>              Labels: beginner
>
> Pretty printing is undesirable for many use cases. This applies to both XML pretty printing and JSON pretty printing. The XMLInfosetOutputter constructor already takes a 'pretty' boolean parameter, but we don't have any way for the CLI to change this constructor parameter's value from true to false in the places where the codebase passes true.
> The issue we need to resolve is how do we let a CLI option change InfosetOutputter settings such as pretty printing XML or using CDATA to preserve whitespace in XML text?
> InfosetOutputters created by the user or the CLI don't have any access to tunables when they are created. The only parts of Daffodil that have access to tunables are the Compiler/ProcessorFactory/DataProcessor which have withTunable/withTunables functions.
> One opinion is the CLI option could use the same {{-T}} flag and the CLI could just figure out which key/value pairs are tunables and which are InfosetOutputter parameters.  Another opinion is that feels like a bit of a hack and the CLI should have another option (maybe -i to match -I for infoset types).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)