-
Notifications
You must be signed in to change notification settings - Fork 11
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
Hook up to MobX Developer Tools #43
Comments
Yes, it's in the todo list ;-) |
@jspuij This is very interesting. Could you tell me if you were thinking of supporting the Mobx/Redux debugger tools or intended to provide an API for developing them? It wasn't clear from your response. If it's the former, would we be recommended to use a predictable state structure (like MST, for instance) to aid with the compatibility with them? I'm very new to these state managers, so apologies if this is a nonsense question. I really wanted to use Mobx over Redux and your implementation seems like the most robust for Blazor. I just want to make sure that replayability is going to be possible (without a major re-write). |
It is going to be possible. However a.t.m. Cortex.Net is unopinionated regarding the structure of its models. Like you suggested, if I want to use the original tools and support them I need at least a tree. I'm not very fond of porting MST and its syntax to C#. It just does not suit it very well. I'll have to come up with something myself for it. (maybe inspired by mobx-keystone, but without all the extra attributes). Anyway, it will come some day ;-) |
OK. Interesting. Thanks for letting me know! |
This is mainly a forward looking question about future functionality. Is there a reasonable prospect that Cortex.Net might be hooked up to a browser developer extension such as MobX Developer Tools to enable runtime inspection of Observable state?
If not, are there any API's in Cortex.Net that would enable me to develop a state inspection popup view in my Blazor application to display a snapshot of observable state on-demand?
The text was updated successfully, but these errors were encountered: