Then you can edit it in the form, it doesn't go into state
Now, you can also reduce the values of
Action.Customer into state if there are multiple pieces of state holding customer information so that, for example, fetching a Customer from the server with a name that has been updated will update existing state
But your state is readonly
SubscribeToAction is a shortcut
Ordinarily you'd take the DTO from the API, reduce its values into state, and then the form would make a copy of that state into a mutable object
but that's a lot of work
I'm not so keen on that
Ordinarily you'd take the DTO from the API, reduce its values into state, and then the form would make a copy of that state into a mutable object
The first part I understand, reducing the values into the state, but how do I make a copy of the state into a mutable object in the component?
Either do the api calls in your app and only reduce results, or ( I recommend) use the action subscriber to grab the mutable DTO from the server and don't let it go into state
assume I have a state with with a huge array of trades (1000+). The UI is build out of many Fluxorcomponents. All of those components show lists which are build from subsets of the state array.
eg:
- List of trades for Apple stock
- List of trades for Microsoft stock
When I insert a new trades to the array in the state for performance reasons only affected components should be updated.
Or is this nothing I should be concerned about?
My assumption is that FluxorComponent calls StateHasChanged in any coponent, also when the add or insert does not affect this component. But I can be wrong. Still studying the code. My concern would be performance in a high traffic realtime application
The ticket is marked Won't Do, with an explanation
So only states + effects + actions could be in the satellite assemblies and not services
So you are starting to tie them in to the main download
@hoangdovan what kind of size difference are you seeing?
I see that a standard (empty) NetStandard2.0 dll is 3.5KB
So yeah, I'd like to know the size of your dlls please
@mrpmorris Thank you so much! We just want to evaluate Blazor for future projects. Yes, you're right, the dll in most case is not so big. The bundle size is just one reason, another reason is separation of concern, we don't want to add everything in main class. Currently we use Angular & Ngrx, and lazy load everything is our standard. Thank for your explanation!
That's fine, you can tell Fluxor to scan multiple assemblies, not just one
Although my gut says only separate out effects + states
have a single shared DLL for all the actions. That way all reducers can react to all actions that should affect their state
@zHaytam thanks, this was my assumption, and trying to find a way to prevent this. I assume those renders will cause performance bottlenecks later in a highly reactive website with lots of changes to the data
So now you have the ability to decide if the component should re-render or not
When the subscription triggers, check if last value != new value. If that is the case then call StateHasChanged
I would use a ReadOnlyDictionary<string, whatever> in the state so I can do an immediate lookup of the data you want, rather than doing a sequential scan of the data with LINQ's
.Where
If you use the new
record in C# 9 for all your state then object equality is done for you for free