BaSyx Editor Extention#1230
Conversation
Function for Validation and Plausibilty of .XML, .KEB, .VEC-Files
Import the XMLValidator and change the FileInput so that an Error in Validation is visible.
New: IODD-Plausibility
Unit tests for the XMLValidator.
Co-authored-by: Copilot <copilot@github.com>
Tests for AAS generation with Kbl and Vec files.
…shes. Co-authored-by: Copilot <copilot@github.com>
removed comments
|
@aaronzi User Manual zum PR und den zugehörigen Issues findet sich hier: |
|
We have set up a demo server where you can test the frontend changes from this pull request: Please note that this demo only hosts the frontend. Since our changes are limited to the BaSyx Web UI frontend, you will need to enter your own backend instance for testing. |
|
Thanks for the PR and the demo. Would all of you be so kind to sign the Eclipse Contributor agreement using the same mail address you used for your git commits. Otherwise I won't be able to merge your PR. Also please resolve the merge conflicts that are currently there by either rebasing or merging the main branch into your fork. |
|
Thanks for signing the ECA. I can see that there are quite a few linting errors in your code. Most of them will probably be fixable by running |
|
I fixed the lint issues and verified locally with A large part of the latest commit normalizes CRLF line endings to LF because the lint rules require LF. The actual code changes are limited to the lint fixes and conflict resolution. |
|
Thanks for fixing most of the problems. There are a few linting errors left. Could you please have a look at them |
BaSyx Editor Extention
Description of Changes
This pull request addresses the following issues:
[FEATURE] File Validation for XML, KBL, VEC #1179
[FEATURE] XML Tree View with Distinguishable Node Labels and Navigation #1200
[FEATURE] Import AAS from .KBL and .VEC files #1201
Related Issue
#1179
#1200
#1201
BaSyx Configuration for Testing
No special configuration is required. We used the Docker container in Docker for Windows as the backend and relied on the standard npm configuration provided by this repository during development.
AAS Files Used for Testing
No special .aas files are required.
We used .vec and .kbl files to generate .aas files and test file validation (Issues #1201 and #1179).
To test the XML viewer, we used random submodels (XML-based files) we uploaded into any aas file(Issue #1200).
All the files we used can be found here:
https://github.com/DHBW-TINF24F/Team3-Basyx-Editor/tree/main/PROJECT/Testfiles
Additional Information
We are a group of students at DHBW Stuttgart who carried out this project as part of Markus Rentschler’s (@mrentsch65) software engineering course.
https://github.com/DHBW-TINF24F/Team3-Basyx-Editor
https://github.com/DHBW-TINF24F/Team3-basyx-aas-web-ui
@FedeZ7
@martin-tinf24f
@fix730
@forestpit
@Loitt2
@Florian-Zahn