Skip to content

Feature Request: If a dependent service is not available for a module, register it? #85

Description

@SimonDarksideJ

In the original configuration layout, certain services, such as the Input Service was always included with the default configuration.

However, since the recent updates, when you "Configure" the Reality Toolkit, no services are pre-loaded. By default, this is not an issue until you install a platform with configuration that requires services such as the Input Service or Boundary System.

Requested update

Ideally, either

  • The Core configuration needs to include the default Input / Boundary or other core services when "Configure" is used. (or)
  • When a platform profile installation is run, if a dependent service is not installed, the default instance of that service needs configuring (The Input Service for controller configuration, the boundary service for a boundary module)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions