Hi @II11II 👋
Thanks for opening an issue!

The latest version of the weather app is using hydrated_bloc to cache the weather information so that it is available offline. Is there something in particular that you're having trouble achieving? I think the weather app should provide a good overview of how you could use hydrated_bloc to accomplish what you're asking for. Thanks 🙏

Hi @felangel 🖐,

Yes, there are some trouble to save nested data using hydrated bloc.

The example of dilemma i provided above.

Here example:
Feature as Developer should create using hydrated bloc
https://vimeo.com/539327490

Here example:
Feature as Developer should create using hydrated bloc
https://vimeo.com/539327490

Is there a code example?

Here example:
Feature as Developer should create using hydrated bloc
https://vimeo.com/539327490

Is there a code example?

Hi @kovacbb 🖐

Actually, I could not write good code for state and bloc and wrote using streams + sqflite it. So there is no code I can provide where the hydrated bloc is used, for that, I asked for example for such kind of feature using hydrated bloc😅

@felangel What if I have multiple states (that extends from a parent state) with different properties. Can I use hydrated_bloc in that case, or I have to stick to the parent state and wrap all the properties inside that?

@felangel What if I have multiple states (that extends from a parent state) with different properties. Can I use hydrated_bloc in that case, or I have to stick to the parent state and wrap all the properties inside that?

You can still use HydratedBloc in that case. You just need to adjust the toJson and fromJson implementations to check the type of the state and perform the correct (de)serialization.

In case @II11II or anyone else may be helped by this:
The way i started to prefer using hydrated_bloc for complex use cases & state classes is by:

1. storing the state class name state.runtimeType.toString() in the toJson() method of each child state class.
2. making a factory public fromJson() in the parent abstract state class, which will call specific child constructors based on the string state value stored in step 1.
3. if there are any variables defined in the abstract parent class, i also make a private fromJson() in the parent abstract class, which will set it's values , and will be called with :super._fromJson() in the child state classes.

this way i can use one-liners for fromJson() and toJson() in the cubit class,
deferring the specifics to the state classes, can define variables in abstract parent state classes,
and also can not repeat code and variables in child constructors.