XML parser does not parse edge IDs #142

Mati-AAU · 2022-12-14T12:10:28Z

Projects loaded with XML are currently given "NotImplemented" as value for their edge ID

Does not cause issues right now because the edge IDs are only used for communication with GUI, and i believe most things currently happen through the JSON parser, although ofcourse can cause issues if XML is going to be wider used.

…y query (#142) This commit solves parsing of universal and inconsistent locations. The previous commits in main can make the internal representation for any single location from a query. However, when combining components, it only support locations that are not universal or inconsistent. We have add a extra field `add` in the enum type `LocationType` to represent any location in for the particular component. We have refactored `get_state` function and spilled some of it content into some sub functions. The method `compare_partial_locations` in `LocationID` is removed and moved to `LocationTuple` with extra addition code to handle comparing of universal or inconsistent locations The method `get_location` in `TransitionSystem` returns the `LocationTuple` for the given `LocationID` input argument The method 'get_combined_decls' combines the individual declaration of components into one declaration. This method is used for `apply_constraints_to_state` in extract_state.rs

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

XML parser does not parse edge IDs #142

XML parser does not parse edge IDs #142

Mati-AAU commented Dec 14, 2022 •

edited

Loading

XML parser does not parse edge IDs #142

XML parser does not parse edge IDs #142

Comments

Mati-AAU commented Dec 14, 2022 • edited Loading

Mati-AAU commented Dec 14, 2022 •

edited

Loading