Skip to content

Conversation

@s-heppner
Copy link

This removes the JSON Schema and XSD files that
stem from the aas-specs repository.
Instead, this adds the logic in the CI to fetch
these files at runtime.

Furthermore, we skip the unittests that make use
of the schema files when they do not exist.

@s-heppner s-heppner marked this pull request as draft March 14, 2024 04:22
@s-heppner s-heppner marked this pull request as ready for review March 14, 2024 04:30
@jkhsjdhjs
Copy link

Very good approach IMO, I think downloading the schema files via the CI and only testing with them if they're present is the right way.

This removes the JSON Schema and XSD files that
stem from the aas-specs repository.
Instead, this adds the logic in the CI to fetch
these files at runtime.

Furthermore, we skip the unittests that make use
of the schema files when they do not exist.
@s-heppner s-heppner merged commit e8aae35 into Extract/ComplianceTool Mar 15, 2024
@s-heppner s-heppner deleted the Extract/Schema branch March 15, 2024 14:07
Frosty2500 pushed a commit that referenced this pull request Nov 11, 2024
Adapt Dockerfile to new BaSyx-Python SDK repository structure
Ornella33 added a commit that referenced this pull request Jan 13, 2025
Adapt Dockerfile to new BaSyx-Python SDK repository structure
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.

3 participants