Feature/#2/create enums for solver types#69
Open
olivierPigeon-RTE wants to merge 6 commits intomainfrom
Open
Conversation
olivierPigeon-RTE
force-pushed
the
feat/#2/create-enums-for-solver-types
branch
from
79adb2b to
3e2e6e1
Compare
Signed-off-by: Olivier Pigeon <olivier.pigeon@rte-france.com>
Signed-off-by: Olivier Pigeon <olivier.pigeon@rte-france.com>
Signed-off-by: Olivier Pigeon <olivier.pigeon@rte-france.com>
…istency Signed-off-by: Olivier Pigeon <olivier.pigeon@rte-france.com>
Signed-off-by: Olivier Pigeon <olivier.pigeon@rte-france.com>
olivierPigeon-RTE
force-pushed
the
feat/#2/create-enums-for-solver-types
branch
from
3e2e6e1 to
2b92c3e
Compare
Signed-off-by: Olivier Pigeon <olivier.pigeon@rte-france.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Does this PR already have an issue describing the problem?
Fixes #2
What kind of change does this PR introduce?
This PR replaces several string values bay enums to be more resilient and avoid typos
Does this PR introduce a breaking change or deprecate an API?