Skip to content

decouple concerns from bus/workshop #205

@JarbasAl

Description

@JarbasAl

this module started as common utils for mycroft-core , nowadays it does some things that belong to other modules

packaging problems:

  • every other ovos package depends on utils, utils can not depend on any other ovos package
  • some utils need ovos-config, this is usually handled by falling back to a default value
  • some utils need a bus connection, FakeBus is a possibility for mocking but realistically none of this code can be used without ovos-bus-client

proposal:

  • move common bus api wrappers to ovos-bus-client or ovos-workshop
  • remove dead code 0.1.0 alpha 1 #204

Consuming services via bus -> ovos-bus-client :

Providing services via bus -> ovos-workshop :

Other utils

  • skill directories related to loading skill entrypoints/paths and depends on OPM -> ovos-plugin-manager
  • mark1 should become part of the phal plugin, keep all mark1 related code there

Metadata

Metadata

Labels

packagingrefactorcode improvements with no functional changes

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions