Closed pjeanmarie closed 3 months ago
Don't merge before https://github.com/powsybl/powsybl-open-rao/pull/920
First review. Also if we do not bump version of crac now when will we be doing it ? Usually PR that break compatibility also bump version of json in other powsybl project.
I did not increase the crac version since the 2.4 is not yet released and so to not increase number on unreleased version, the 2.4 will contains multiple changes included this one, the TwoSides one and at least one other. (@pet-mit )
@pjeanmarie Also I saw that you kept the old deserializer, and added new deserializer for the new actions. Because the format is not so different in terms of data, maybe we can use only the new deserializer even for retrocompatibility, like it is usually done in powsybl-core ?
First review. Also if we do not bump version of crac now when will we be doing it ? Usually PR that break compatibility also bump version of json in other powsybl project.
I did not increase the crac version since the 2.4 is not yet released and so to not increase number on unreleased version, the 2.4 will contains multiple changes included this one, the TwoSides one and at least one other. (@pet-mit )
@obrix @pet-mit Since crac 2.4 version was released with Rao v6.0.0, I will create new version 2.5.
Also please update the documentation
done
@pjeanmarie Also I saw that you kept the old deserializer, and added new deserializer for the new actions. Because the format is not so different in terms of data, maybe we can use only the new deserializer even for retrocompatibility, like it is usually done in powsybl-core ?
As discussed, we can have now many deserializer (different action type) where we had only one previously and the format is a bit different so not easy code factorisation here.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
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: