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

Tag parsing in XML documents #352

Open
g-psantos opened this issue Dec 8, 2022 · 2 comments
Open

Tag parsing in XML documents #352

g-psantos opened this issue Dec 8, 2022 · 2 comments
Labels

Comments

@g-psantos
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I have a project where some requirements are implemented via settings recorded in an XML configuration file. OFT currently does not support importing tags from XML files, as documented in the User Guide:

Note that XML is at the moment not yet supported by the Tag Importer, because it would collide with the SpecObj Importer. Once import fallback is implemented, XML will be supported too.

Describe the solution you'd like
I would like to be able to add implementation tags to an XML file and have those parsed by OFT when tracing requirements.

It looks like the comment about import fallback was added 3 years ago. Is this something that's still on the radar to implement?

Describe alternatives you've considered
As a workaround, I can document the implementations in a separate Markdown file that references the XML file and add a comment to the XML file that notes that the setting is implementing a requirement. However, this separates the implementation tag from the actual implementation (somewhat needlessly).

@redcatbear
Copy link
Collaborator

Hi @g-psantos, in the current implementation OFT picks the importer by file suffix from a list of supported importers. The first importer to feel responsible for a file suffix wins. This is why currently we try to only support each suffix by only one importer.

So with the current implementation you could trick OFT into using the tag importer by changing the file suffix. I know that this is not very convenient, but we first need to implement a project-central configuration in a separate ticket before being able to override such settings.

@redcatbear
Copy link
Collaborator

Depends on #353 (central configuration).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 📫 Backlog
Development

No branches or pull requests

2 participants