Skip to content

Get rid of adapter layer in favour of providerRegistry #310

Description

@s1hofmann

Short overview
Having the providerRegistry makes the adapter layer obsolete

Detailed description
After introducing the providerRegistry there's no real need for the adapter layer.
Both vision and native adapter should be removed and tests adapted to use the providerRegistry instead

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintenanceMaintenance tasks to keep code clean and up-to-date

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions