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

tags cannot parse in cp arxml #123

Open
hogger0 opened this issue Oct 30, 2024 · 5 comments
Open

tags cannot parse in cp arxml #123

hogger0 opened this issue Oct 30, 2024 · 5 comments

Comments

@hogger0
Copy link

hogger0 commented Oct 30, 2024

RootComposition3.arxml(16): Unprocessed element
RootComposition3.arxml(52): Unprocessed element
RootComposition3.arxml(64): Unprocessed element
RootComposition3.arxml(149): Unprocessed element
RootComposition3.arxml(347): Unprocessed element
RootComposition3.arxml(757): Unprocessed element
RootComposition3.arxml(956): Unprocessed element
RootComposition3.arxml(1191): Unprocessed element
RootComposition3.arxml(1802): Unprocessed element
RootComposition3.arxml(1827): Unprocessed element

@cogu
Copy link
Owner

cogu commented Oct 30, 2024

I've checked the implementation and it's supposed to print the tag name wrapped in "<>" right after "Unprocessed element".

Anyway, it doesn't matter. The message simply means that an XML element is not yet implemented and I am fully aware which elements are not yet implemented in v0.5.

If you don't add additional information to this issue I will close it.

@hogger0
Copy link
Author

hogger0 commented Oct 30, 2024

RootComposition3.arxml(16): Unprocessed element <DATA-TRANSFORMATION-SET
RootComposition3.arxml(52): Unprocessed element <GENERAL-PURPOSE-PDU
RootComposition3.arxml(64): Unprocessed element <I-SIGNAL-I-PDU
RootComposition3.arxml(149): Unprocessed element <I-SIGNAL
RootComposition3.arxml(347): Unprocessed element <SYSTEM-SIGNAL
RootComposition3.arxml(757): Unprocessed element <SO-AD-ROUTING-GROUP
RootComposition3.arxml(956): Unprocessed element <SYSTEM
RootComposition3.arxml(1191): Unprocessed element <ETHERNET-CLUSTER
RootComposition3.arxml(1802): Unprocessed element <COUPLING-ELEMENT
RootComposition3.arxml(1827): Unprocessed element <ECU-INSTANCE

@hogger0
Copy link
Author

hogger0 commented Oct 30, 2024

I've checked the implementation and it's supposed to print the tag name wrapped in "<>" right after "Unprocessed element".

Anyway, it doesn't matter. The message simply means that an XML element is not yet implemented and I am fully aware which elements are not yet implemented in v0.5.

If you don't add additional information to this issue I will close it.

RootComposition3.arxml(16): Unprocessed element <DATA-TRANSFORMATION-SET
RootComposition3.arxml(52): Unprocessed element <GENERAL-PURPOSE-PDU
RootComposition3.arxml(64): Unprocessed element <I-SIGNAL-I-PDU
RootComposition3.arxml(149): Unprocessed element <I-SIGNAL
RootComposition3.arxml(347): Unprocessed element <SYSTEM-SIGNAL
RootComposition3.arxml(757): Unprocessed element <SO-AD-ROUTING-GROUP
RootComposition3.arxml(956): Unprocessed element <SYSTEM
RootComposition3.arxml(1191): Unprocessed element <ETHERNET-CLUSTER
RootComposition3.arxml(1802): Unprocessed element <COUPLING-ELEMENT
RootComposition3.arxml(1827): Unprocessed element <ECU-INSTANCE

@hogger0
Copy link
Author

hogger0 commented Oct 30, 2024

These labels are not implemented?

@cogu
Copy link
Owner

cogu commented Oct 30, 2024

That's right. None of them are implemented yet and won't be for a very long time. Some of the system-related ones isn't planned until v0.8.
You can always check the CHANGELOG to see which elements are currently supported.

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

2 participants