gems issueshttps://git.esa.informatik.tu-darmstadt.de/gems/gems/-/issues2018-10-21T18:09:54Zhttps://git.esa.informatik.tu-darmstadt.de/gems/gems/-/issues/3Refactor FeasibleMinIIProperty2018-10-21T18:09:54ZSebastian VollbrechtRefactor FeasibleMinIIPropertyJust like issue #2, the FeasibleMinIIProperty is responsible for too many things right now. Some steps should be refactored/extracted/documented and tested properly (e.g. node placement, edge creation, ...).Just like issue #2, the FeasibleMinIIProperty is responsible for too many things right now. Some steps should be refactored/extracted/documented and tested properly (e.g. node placement, edge creation, ...).Sebastian VollbrechtSebastian Vollbrechthttps://git.esa.informatik.tu-darmstadt.de/gems/gems/-/issues/2Refactor InfeasibleMinIIProperty & resolve TODOs2018-10-21T18:24:37ZSebastian VollbrechtRefactor InfeasibleMinIIProperty & resolve TODOsThe InfeasibleMinIIProperty class is responsible for too many things right now. Some steps should probably be refactored and tested properly and independently from the generation process as a whole (e.g. node placement).The InfeasibleMinIIProperty class is responsible for too many things right now. Some steps should probably be refactored and tested properly and independently from the generation process as a whole (e.g. node placement).Sebastian VollbrechtSebastian Vollbrecht