-
Notifications
You must be signed in to change notification settings - Fork 3
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
When SCL Namespace isn't the default #80
Comments
We have decided to - within the ongoing refactor - create our own query function that will allow setting any namespace as the default namespace in the future. My guess is that mid-Dec it will be available for you to use. |
@dlabordus @Sander3003 This one can be closed right? |
Agree |
I kind of disagree, because the XML is valid if it's not the default namespace, but it seems the electric world expect it to be the default. |
Hello there, Thank you for opening this issue! We appreciate your interest in our project. If you believe this issue is still relevant and requires attention, please provide any additional context, updates, or details that might help us understand the problem better. If the issue is no longer relevant, you can simply close it. If you're uncertain, you can always reopen it later. Remember, our project thrives on community contributions, and your input matters. We're here to collaborate and improve. |
Background:
When a SCL XML File is used that doesn't use the SCL Namespace as the default namespace the OpenSCD editor isn't working correctly, because it expects it to be the default. The file is loaded and parts of the XML can be edited, but some parts won't.
The text was updated successfully, but these errors were encountered: