Changes to remove config models.

[TeresiaOlsson]

I have started a PR to remove the config models and include the changes for the schema registry to work for this packages.

It should maybe not be merged until a new release of pyaml has been done since it needs the validation model of pyaml.

@gupichon I have one problem with the static catalog where I'm not sure about the best solution. It includes:

    def resolve(self, key: str) -> BaseModel:
        try:
            return self._refs[key]._cfg  # --> What is supposed to be returned here?
        except KeyError as exc:
            raise PyAMLException(f"StaticCatalog cannot resolve key '{key}'") from exc

As I understand it self._refs[key] returns a DeviceAccess object which doesn't have an interface for returning the configuration of it. I guess it only has worked so far because DeviceAccess has been inherited and the subclasses have all implemented a _cfg attribute despite that it's not part of the defined interface. So now when there is no _cfg anymore, what should actually be returned here? And maybe that should be included in the DeviceAccess interface to make sure all future subclasses implement it?

[read-the-docs-community]

Documentation build overview

📚 pyaml-cs-oa | 🛠️ Build #34257055 | 📁 Comparing 2bf5236 against latest (40327d3)

  🔍 Preview build  

16 files changed · ± 12 modified · - 4 deleted

± Modified

• api.html
• genindex.html
• py-modindex.html
• api/pyaml_cs_oa.container.html
• api/pyaml_cs_oa.epics.html
• api/pyaml_cs_oa.epicsR.html
• api/pyaml_cs_oa.epicsRW.html
• api/pyaml_cs_oa.epicsW.html
• api/pyaml_cs_oa.html
• api/pyaml_cs_oa.signal.html
• and 2 more...

- Deleted

• api/pyaml_cs_oa.controlsystem.html
• api/pyaml_cs_oa.dynamic_catalog.html
• api/pyaml_cs_oa.static_catalog.html
• api/pyaml_cs_oa.static_catalog_entry.html