Code Monkey home page Code Monkey logo

Comments (4)

StevenTCramer avatar StevenTCramer commented on July 18, 2024

Thanks for using blazor-state and take the time to give your input.
I will be updating to 3.1 this weekend. So if this is something we determine beneficial it could make it in.

Can you give me an example use case?
I am thinking you probably have your own base component in your code that you could implement Dispose on?

The BlazorStateComponent is ensuring it clears the stuff it responsible for.

from blazor-state.

AbeBaehaki avatar AbeBaehaki commented on July 18, 2024

In my case, I needed to update a state when a component is disposed. My first attempts is to hide the BlazorStateComponent Dispose method in my component, but that did not work.

Then I figure I can create my own base component, but seems like I would need to manage the component state change manually? Since if I were to create a GetState method, the Subscriptions.Add only accept component of type BlazorStateComponent .

    protected T GetState<T>()
    {
      Type stateType = typeof(T);
      Subscriptions.Add(stateType, this);
      return Store.GetState<T>();
    }

I guess changing Subscriptions.Add method to accept IBlazorStateComponent interface instead can be an option. Or maybe my assumption of how the component state changes are handled is wrong?

Also, thank you for creating such an awesome library. 👍

from blazor-state.

StevenTCramer avatar StevenTCramer commented on July 18, 2024

Have your base component inherit from BlazorStateComponent. Then you can dispose your stuff and it will manage the subscritpions.

from blazor-state.

AbeBaehaki avatar AbeBaehaki commented on July 18, 2024

Aha! I see. So seems like I missed a small but important detail here.

    public class MyComponentBase1 : BlazorStateComponent
    {
        public new void Dispose()
        {
            throw new Exception("WILL NOT BE CALLED");
            base.Dispose();
        }
    }

    public class MyComponentBase2 : BlazorStateComponent, IDisposable
    {
        public new void Dispose()
        {
            throw new Exception("WILL BE CALLED");
            base.Dispose();
        }
    }

Previously, I wrote my base component like the MyComponentBase1 in the snippet and the dispose does not work as expected. After I changed it like the MyComponentBase2, then It works.

Thank you! I will now close this issue.

from blazor-state.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.