Is your feature request related to a problem? Please describe.
Currently with gridappsd-python dependent on cim-graph and cim-graph dependent on a version of gridappsd-python there is a circular reference that is really difficult to get around. cim-graph depends only on the connection for gridappd-python but not the other items, whilst it's only the field-messagebus that depends on cim-graph. By separating these into a secondary project/wheel we can avoid this issue.
Describe the solution you'd like
Change gridappsd-python into a mono-repository which would have two different wheels being built out of it. See https://gitlab.com/craig81/poetry-monorepo as an example of what I would like to do.
Describe alternatives you've considered
An alternative is to break this repo into multiple repositories, however I don't think that this is a good idea.
Is your feature request related to a problem? Please describe.
Currently with gridappsd-python dependent on cim-graph and cim-graph dependent on a version of gridappsd-python there is a circular reference that is really difficult to get around. cim-graph depends only on the connection for gridappd-python but not the other items, whilst it's only the field-messagebus that depends on cim-graph. By separating these into a secondary project/wheel we can avoid this issue.
Describe the solution you'd like
Change gridappsd-python into a mono-repository which would have two different wheels being built out of it. See https://gitlab.com/craig81/poetry-monorepo as an example of what I would like to do.
Describe alternatives you've considered
An alternative is to break this repo into multiple repositories, however I don't think that this is a good idea.