Any reason to implement IServiceBundle or extend AbstractServiceBundle? about loxodon-framework

[vovgou]

Hi，IServiceBundle cannot solve your needs, it is just a service container similar to IoC/DI.
You can use Addressable Asset System or Loxodon.Framework.Bundle to load assets asynchronously.

Can you speak Chinese? If you have QQ, please add my QQ group 622321589

[heshuimu]

Hi，IServiceBundle cannot solve your needs, it is just a service container similar to IoC/DI.

I think I am now aware of that. But, it seems to me that I can make a service bundle class that does not implement the interface and can still properly set up and tear down services. My sense is that I would not lose any extra functionalities if I don't implement the interface, but I wanted to confirm.

Here's what I ended up with:

using UnityEngine;
using Loxodon.Framework.Services;
using Loxodon.Framework.Asynchronous;

#nullable enable

// Does not implement IServiceBundle
public class GameDriverServiceBundle
{
	private readonly IServiceContainer serviceContainer;

	public GameDriverServiceBundle(IServiceContainer serviceContainer)
	{
		this.serviceContainer = serviceContainer;
	}

	public async Task Start()
	{
		GameObject? original = await LoadAsync<GameObject>("GameDriverSupportingComponents");
		GameObject newInstance = Object.Instantiate(original!);

		// Set up example:
		serviceContainer.Register("GameCamera", newInstance.GetComponentInChildren<Camera>());
	}

	public void Stop()
	{
		// Tear down
		serviceContainer.Unregister("GameCamera");
	}

	private static async Task<T?> LoadAsync<T>(string path) where T : Object
	{
		return await Resources.LoadAsync<T>(path) as T;
	}
}

[vovgou]

Yes, you are right.

But please do not store GameObject in ServiceContainer, it is an IoC container, storing business logic services or basic components in the container, such as network components, role backpack services, etc.

Maybe you can store your game object in PlayerContext or ApplicationContext.