Skip to content

Feature/352 tag parsing in xml documents#532

Merged
redcatbear merged 11 commits into
mainfrom
feature/352_tag-parsing-in-xml-documents
Jun 1, 2026
Merged

Feature/352 tag parsing in xml documents#532
redcatbear merged 11 commits into
mainfrom
feature/352_tag-parsing-in-xml-documents

Conversation

@redcatbear
Copy link
Copy Markdown
Collaborator

Introduced priorities in importer factories to allow having more than one supporting a file extension and still getting back a single result in a controlled manner.

This allowed me to introduce .xml in the tag importer. The tag importer has a lower priority than the SpecObject importer. Since the SpecObject importer peeks into the XML files and refuses to support them when the expected header is missing, the tag importer gets its chance on non-SpecObject XML.

@g-psantos , that should do the trick for annotating regular XML files with coverage. I know, this one has been long in the making, but I needed to figure out a way that could be done with minimal changes.

Closes #352.

@redcatbear redcatbear self-assigned this May 31, 2026
@redcatbear redcatbear requested a review from kaklakariada May 31, 2026 12:03
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 1, 2026

@redcatbear redcatbear merged commit ef4f368 into main Jun 1, 2026
11 checks passed
@redcatbear redcatbear deleted the feature/352_tag-parsing-in-xml-documents branch June 1, 2026 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tag parsing in XML documents

2 participants