Split models.yml

[bastianjoel]

We should check if the workaround introduced in OpenSlides/openslides-autoupdate-service#907 can be removed.

The corresponding issue in go-yaml was closed.

[ostcar]

@bastianjoel I don't know, if this is possible. See my comment here: OpenSlides/openslides-autoupdate-service#907 (comment)

Could you have a look if it is possible? If not, I would like to close this

[bastianjoel]

The solution would be to move all models into a property as we were already about to do in https://github.com/OpenSlides/openslides-meta/pull/12/files

[ostcar]

I would like this.

I move this issue to the meta-repo, since since this chance should be discussed there

[ostcar]

The Idea of this issue is, to change the structure of the models.yml.
Currently, the hole file is one dictionary/map from collection-name to the collection. The problem with this structure is, that there is no namespace for meta-data. So the structure should be changed to put all collections one step down to have a place for meta-data next to the collections.

for example:

collections:
  motion:
    ...
  user:
    ...
  ...
meta:
  ...

[ostcar]

We discussed:

We think, what we should do this and we should do it now, before we start the postgres-changes.

We also think, that it could be interesting, if each collection would be in one separate file, linked/included in one central "models.yml". Before we make a final decision, we have to check, that all our yaml-libs support it.

• Go
• Python
• Typescript