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

fix: Adding Subnetwork to a configuration without a Communication Ele… #875

Conversation

pascalwilbrink
Copy link
Member

@pascalwilbrink pascalwilbrink commented Jul 14, 2022

closes #847
…ment failed for the first time

When creating a Communication Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard

The Should create a Communication Element integration test is extended to also check that the Wizard is closed properly

Signed-off-by: Pascal Wilbrink pascal.wilbrink@alliander.com

…ment failed for the first time

When creating a `Communication` Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard

The `Should create a Communication Element` integration test is extended to also check that the Wizard is closed properly

Signed-off-by: Pascal Wilbrink <pascal.wilbrink@alliander.com>
…ment failed for the first time

When creating a `Communication` Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard

The `Should create a Communication Element` integration test is extended to also check that the Wizard is closed properly

Signed-off-by: Pascal Wilbrink <pascal.wilbrink@alliander.com>
…ment failed for the first time

When creating a `Communication` Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard

The `Should create a Communication Element` integration test is extended to also check that the Wizard is closed properly

Signed-off-by: Pascal Wilbrink <pascal.wilbrink@alliander.com>
…ment failed for the first time

When creating a `Communication` Element in Communication.ts, the created Element is also returned to use it as a parent for the wizard

The `Should create a Communication Element` integration test is extended to also check that the Wizard is closed properly

Signed-off-by: Pascal Wilbrink <pascal.wilbrink@alliander.com>
Copy link
Collaborator

@JakobVogelsang JakobVogelsang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some line in the test are not needed and make the test less readable. I would suggest refactoring a bit more.

@JakobVogelsang JakobVogelsang self-requested a review July 19, 2022 11:52
Copy link
Collaborator

@JakobVogelsang JakobVogelsang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@pascalwilbrink pascalwilbrink merged commit 0f661d4 into main Jul 20, 2022
@pascalwilbrink pascalwilbrink deleted the 847_Adding_Substation_Without_Communication_Element_Present_Fails_First_Time branch July 20, 2022 07:50
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

Successfully merging this pull request may close these issues.

Adding SubNetwork element in COMMUNICATION does not work right away
2 participants