-
Notifications
You must be signed in to change notification settings - Fork 2
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
[IIDM v1.1] Migration of XNode extension to the new design #36
Projects
Comments
sebalaig
added a commit
that referenced
this issue
May 19, 2020
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
5 tasks
mathbagu
pushed a commit
that referenced
this issue
Jun 5, 2020
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr> Signed-off-by: Mathieu BAGUE <mathieu.bague@rte-france.com>
mathbagu
pushed a commit
that referenced
this issue
Jun 5, 2020
mathbagu
pushed a commit
that referenced
this issue
Jun 11, 2020
mathbagu
pushed a commit
that referenced
this issue
Jun 11, 2020
mathbagu
pushed a commit
that referenced
this issue
Jun 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Feature
Extensionxnode powsybl-core#1153
Merging view : variant manager implementation powsybl-core#1091
What is the current behavior?
The XNode extension use the old design.
What is the expected behavior?
The XNode extension should use the new design of extensions.
What is the motivation / use case for changing the behavior?
Have both Java and C++ API as close as possible
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered: