stevedlawrence commented on PR #1582: URL: https://github.com/apache/daffodil/pull/1582#issuecomment-3473534627
> Consider adding a switch to escalate this to an error. (or maybe we need a global switch to escalate all warnings that are not explicitly suppressed to errors) Just a note, in testing I did see some regression schemas that generated this warning, but they were either properties that weren't actually used so the order didn't matter, or the property changed to things that were essentially the same (e.g. "US-ASCII" to "us-ascii"). So there are cases where these warnings can be safely ignored. But a switch to promote to an error does seem reasonable for users that want to ensure any changes to property resolution are investigated and fixed. As to the switch, I don't remember this being implemented, but we do actually have the `escalateWarningsToErrors` tunable. I would suggest we use that rather than having a switch specific to this message. And we can us schema in-line warning suppression if there are any warnings that can't be fixed for whatever reason. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
