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

Wrong link reference for Unix Definition Schema #129

Open
marcusburghardt opened this issue Oct 27, 2021 · 1 comment
Open

Wrong link reference for Unix Definition Schema #129

marcusburghardt opened this issue Oct 27, 2021 · 1 comment
Assignees
Milestone

Comments

@marcusburghardt
Copy link

Describe the bug
Some links present at Unix Definitions Schema has a wrong reference which may confuse readers.

I observed that tests which share the same name on both Unix Definition Schema and Windows Definition Schema pages are correctly referenced on Windows Definition Schema page[1] but wrongly referenced on Unix Definition Schema page[2]:

  1. https://oval-community-guidelines.readthedocs.io/en/latest/oval-schema-documentation/windows-definitions-schema.html
  2. https://oval-community-guidelines.readthedocs.io/en/latest/oval-schema-documentation/unix-definitions-schema.html

The following links are wrongly referenced at Unix Definition Schema page:

  • dnscache_test
  • file_test
  • interface_test
  • process_test
  • process58_test

However, checking the source file at the repository, the references looks correct:

Replication Steps
Steps to reproduce the behavior:

  1. Go to https://oval-community-guidelines.readthedocs.io/en/latest/oval-schema-documentation/unix-definitions-schema.html
  2. Click on any of the mentioned links above
  3. Note they will redirect you for the "windows-definitions-schema.html" instead of stay at 'unix-definitions-schema.html' page.

Expected behavior
All links for Unix tests should reference a Unix test and not a Windows test.

@vanderpol vanderpol added this to the 5.12 milestone Sep 30, 2024
@vanderpol
Copy link
Member

@DeafBDoor and/or @A-Biggs, by no means a critical issue, but if you happen to figure out this issue as part of the release/build process that would be great. It has to do with the same test name in UNIX and Windows schema's, but I have no idea why it's causing issues with our generated docs.

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

No branches or pull requests

4 participants