Add private extensions validation (loadflow-validation)#3820
Add private extensions validation (loadflow-validation)#3820samirromdhani wants to merge 3 commits intomainfrom
Conversation
c2285cc to
327b46d
Compare
There was a problem hiding this comment.
The problem with the unit test comes from these lines.
Paths.get(...) retrieves the file from the OS file system, but in the unit test we use a virtual FS.
See for instance how it is done in DynamicSimulationTool: the FS that is used is retrieved from the context.
There was a problem hiding this comment.
Thanks, that’s helpful! I see how using the FS from context's tool.
a0c431d to
9c0abce
Compare
f9eaad5 to
c53de78
Compare
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> add ExtensionsValidation tests Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> WIP Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> add doc Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> test Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> fix fix test Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> test Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
c53de78 to
3a738cb
Compare
|
rolnico
left a comment
There was a problem hiding this comment.
Seems good except for a fix needed in the documentation.
To be sure that everything works fine, it could be tested with an OLF extension for example?
| `--with-extensions-validation`<br> | ||
| Use the `--with-extensions-validation` parameter to perform extensions validation. | ||
|
|
There was a problem hiding this comment.
Wrong place, you put it between an argument and the examples linked to that argument



Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Fixes #696
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: