-
Notifications
You must be signed in to change notification settings - Fork 18
fix: Add capability of having a system object name different than system #96
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
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #96 +/- ##
==========================================
- Coverage 95.36% 95.20% -0.16%
==========================================
Files 8 8
Lines 1638 1688 +50
==========================================
+ Hits 1562 1607 +45
- Misses 76 81 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hi @pesap Thanks for the quick turnaround on this! I’ve run a regression test against my model (where the System object is named "NEM") using the changes in PR #96. I can confirm that the AssertionError is resolved and the property membership is now correctly handled. I verified the internal state of the database using get_object_properties at each step to ensure the Round-Trip (Delete -> Add -> Query) works as expected. Summary Test Results:
LOG OUTPUTS TEST CODE |
No description provided.