Skip to content

fix the ODXLINK reference resolution fallback to ignore the DOCREF attributes #395

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

Closed
wants to merge 1 commit into from

Conversation

andlaus
Copy link
Member

@andlaus andlaus commented Feb 25, 2025

This is only relevant for invalid datasets which specify references with incorrect DOCREF and/or DOCTYPE attributes. This patch should make ODXLINK reference resolution work in non-strict mode for such datasets.

Andreas Lauser <[email protected]>, on behalf of MBition GmbH.
Provider Information

…tributes

this is only relevant for invalid datasets which specify references
with incorrect DOCREF and/or DOCTYPE attributes. This patch should
make ODXLINK reference resolution work in non-strict mode for such
datasets.

Signed-off-by: Andreas Lauser <[email protected]>
Signed-off-by: Alexander Walz <[email protected]>
@andlaus andlaus requested a review from nada-ben-ali February 25, 2025 15:22
@andlaus
Copy link
Member Author

andlaus commented Feb 25, 2025

@nada-ben-ali: this hopefully fixes the root cause of #392. can you verify?

Copy link
Collaborator

@kayoub5 kayoub5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#392 now contains the proper fix for odx 2.0

@andlaus
Copy link
Member Author

andlaus commented Feb 25, 2025

cool, thanks. it is probably a good idea to prop up the reference resolution fallback code anyway, right?

@kayoub5
Copy link
Collaborator

kayoub5 commented Feb 25, 2025

cool, thanks. it is probably a good idea to prop up the reference resolution fallback code anyway, right?

I never saw an OEM file where that would be needed, only exception was the ODX 2.0 files, and that's fixed already

@andlaus
Copy link
Member Author

andlaus commented Feb 26, 2025

fair enough. let's close this...

@andlaus andlaus closed this Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants