Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for service interface inheritance #73

Closed
FejZa opened this issue Mar 4, 2024 · 1 comment
Closed

Add support for service interface inheritance #73

FejZa opened this issue Mar 4, 2024 · 1 comment

Comments

@FejZa
Copy link
Contributor

FejZa commented Mar 4, 2024

Reality Collective - Service Framework Feature Request

Is your feature request related to a problem? Please describe

So this is sorts of an edge case issue and there is many ways to work around it. But maybe something easy enough to fix.

Image the following scenario:

  • A user is using the Reality Toolkit
  • They create a custom input service definition IMyInputService that is defined as public interface IMyInputService : IInputService
  • Then they create an implementation of that service and register it
  • Now all Reality Toolkit services that depend on IInputService will still fail to look it up because IMyInputService is not identified as a valid IInputService
@SimonDarksideJ
Copy link
Contributor

Completed as of #110

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants