You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2020/05/11 14:55:00 UTC

[jira] [Commented] (DAFFODIL-1638) Isolate invalid DFDL schema and XML files so IDEs dont flag them

    [ https://issues.apache.org/jira/browse/DAFFODIL-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104527#comment-17104527 ] 

Mike Beckerle commented on DAFFODIL-1638:
-----------------------------------------

Note: One way to fix this issue, while preserving the TDML-is-invalid tests is to convert them into Scala code where the TDML is a string or XML literal inside scala code. 


> Isolate invalid DFDL schema and XML files so IDEs dont flag them
> ----------------------------------------------------------------
>
>                 Key: DAFFODIL-1638
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1638
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Clean Ups, Infrastructure
>            Reporter: Mike Beckerle
>            Priority: Major
>
> our daffodil source tree has, intentionally, invalid DFDL schema files that cause validation to fail for unit test purposes (negative tests). We should rename these files so they don't cause the Eclipse (or other) IDE to create distracting validation warnings when you have the daffodil source tree open.
> These tests need to explicitly use file names like foo.dfdl.xsd.invalid so that the IDE will not view it as a XSD file and try to validate it.
> This will enable a single setup of Eclipse to be used by persons trying to author DFDL schemas, who want the XML & XSD validation capabilities turned on, and used by persons trying to do daffodil development.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)