Refactor di to di injection collection so when use in lh uploading the package will create error if classes not provided for easy update - di optional and di core - Best done during implementing full component

[Phil-NHS]

[Phil-NHS]

because TELBlazor Components is generic it may need less DI but actually LH implementations will as they will share controller services

so when use in lh uploading the package will create error if classes not provided for easy update

the intention is if you are using all blazor components then you call use the di collection
and it will mean when the package update you will get an error telling you where the program files need it adding to satisfy the injection.

there will be an extension method so if its injected for a contoller already you can drop it in and if it already exists its not overwritten but its explicit blazor components needs it

code notes

//using Blazored.LocalStorage;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Options;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Net.NetworkInformation;
using System.Text;
using System.Threading.Tasks;
using TELBlazor.Components.Core.Configuration;

namespace TELBlazor.Components.Core.DI
{
public static class DI
{
///

/// Adding this to your program.cs will enable Visual Studio to notify you when a package update requires a new service adding
///

///

/// qqqq what if its already injected we will then be requiring a second injection
/// Excludes
///

///
/// client in some occassions will have different scoping
///
public static IServiceCollection AddTELBlazorComponentServices(this IServiceCollection services,
bool IsClient,
ITELBlazorBaseComponentConfiguration TELBlazorBaseComponentConfiguration
)
{

        if (IsClient)
        {
            services.AddSingleton<ITELBlazorBaseComponentConfiguration>(sp => { return TELBlazorBaseComponentConfiguration; });

        }
        else
        {
            services.AddScoped<ITELBlazorBaseComponentConfiguration>(sp => { return TELBlazorBaseComponentConfiguration; });
        }

        //Add Services
        //qqqq not uing this yet, services.AddBlazoredLocalStorage();
        //qqqq come back and refactor client a service to use this
        // qqqq if the controllers already have the service then this would require another to be added and then there would be two the later overides the former but seems innefficient
        // we may require a service thats never used if the consuming project doesnt use it, so it seems it would be useful for lh but actually thats it, or we make them optional.
        return services;
    }


    //private static IServiceCollection TryAddSingletonIfNotRegistered<TService>(
    //this IServiceCollection services,
    //TService instance)
    //{
    //    if (!services.Any(sd => sd.ServiceType == typeof(TService)))
    //    {
    //        services.AddSingleton<instance>(instance);
    //    }
    //    return services;
    //}
    //private static IServiceCollection TryAddScopedIfNotRegistered<TService>(
    //this IServiceCollection services,
    //TService instance)
    //{
    //    if (!services.Any(sd => sd.ServiceType == typeof(TService)))
    //    {
    //        services.AddScoped<instance>(instance);
    //    }
    //    return services;
    //}
}

}