Fix : Wrong root network node maked as built after voltage init modifications#989
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughStudyService.insertVoltageInitModifications now extracts the first present modification result from networkModificationResults.modificationResults() and emits impacts for the supplied rootNetworkUuid instead of iterating over results with an index mapped to studyRootNetworkEntities. ChangesVoltage-init impact notification
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ast-grep (0.42.2)src/main/java/org/gridsuite/study/server/service/StudyService.java[] Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…ications Signed-off-by: Ayoub LABIDI <ayoub.labidi@protonmail.com>
5af5ff8 to
7f267ff
Compare
|
dbraquart
left a comment
There was a problem hiding this comment.
code: ok
tests: ok (with 2 and 3 root networks)



In insertVoltageInitModifications : Modification application contexts are filtered to the target root network but results were indexed against the full root network list, always attributing the built status to the first root network instead of the one voltage init was applied on.