You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As as engineer
I want to have faster feed back when a SCL Name is used
So that I can change it directly before saving/adding the SCL File
Background:
Issue com-pas/compas-scl-data-service#204 implements a Rest API Call to check if a name isn't already used.
This call can be used when saving a new SCL File to CoMPAS or updating the name in the CoMPAS Versions Editor.
When the name is already used block the action (Save/Update) and add a message to the Log Window using a LogEvent.
The text was updated successfully, but these errors were encountered:
Thank you for opening this issue! We appreciate your interest in our project.
However, it seems that this issue hasn't had any activity for a while. To ensure that our issue tracker remains organized and efficient, we occasionally review and address stale issues.
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.
Feel free to continue the conversation here.
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.
Thank you for being part of this journey!
As as engineer
I want to have faster feed back when a SCL Name is used
So that I can change it directly before saving/adding the SCL File
Background:
Issue com-pas/compas-scl-data-service#204 implements a Rest API Call to check if a name isn't already used.
This call can be used when saving a new SCL File to CoMPAS or updating the name in the CoMPAS Versions Editor.
When the name is already used block the action (Save/Update) and add a message to the Log Window using a LogEvent.
The text was updated successfully, but these errors were encountered: