Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move the parsing exception to the model #120

Merged
merged 1 commit into from
Aug 18, 2024
Merged

Move the parsing exception to the model #120

merged 1 commit into from
Aug 18, 2024

Conversation

uhafner
Copy link
Member

@uhafner uhafner commented Aug 18, 2024

It makes no sense to reuse this exception, especially when there are non XML parsers used in the future.

@uhafner uhafner added the internal Internal changes without user or API impact label Aug 18, 2024
Copy link

☀️   Quality Monitor

   🚦   Tests: 100 % successful (✔️ 305 passed)
   〰️   Line Coverage: 96% (86 missed lines)
   ➰   Branch Coverage: 93% (71 missed branches)
   PIT   Mutation Coverage: 90% (109 survived mutations)
   CheckStyle   CheckStyle: No warnings
   PMD   PMD: No warnings
   SpotBugs   SpotBugs: No warnings
   🐛   Error Prone: 82 warnings (0 error, 0 high, 82 normal, 0 low)

Created by Quality Monitor v1.9.0 (#00b9b1a). More details are shown in the GitHub Checks Result.

@uhafner uhafner merged commit 34d7701 into main Aug 18, 2024
31 of 32 checks passed
@uhafner uhafner deleted the xml-exception branch August 18, 2024 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Internal changes without user or API impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant