You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use a custom code that I have as a GrainState, and it should be serialized to azure storage table. I started by developing the logic around my state class using POCO implementation, for which I wasn't required to provide with a public setter for every property that I have. Moreover, some properties intentionally doesn't have any public setter to prevent changing the values externally.
Is there a way to control which properties are serialized with the state and how the state is serialized? If not, is anything planned around this area for the next versions?
Reading the decks from the recent meetups, I spotted a bullet saying there are plans to get rid of the GrainState. What are the exact plans in that area?
Many thanks,
Dotan
The text was updated successfully, but these errors were encountered:
I want to use a custom code that I have as a GrainState, and it should be serialized to azure storage table. I started by developing the logic around my state class using POCO implementation, for which I wasn't required to provide with a public setter for every property that I have. Moreover, some properties intentionally doesn't have any public setter to prevent changing the values externally.
Is there a way to control which properties are serialized with the state and how the state is serialized? If not, is anything planned around this area for the next versions?
Reading the decks from the recent meetups, I spotted a bullet saying there are plans to get rid of the GrainState. What are the exact plans in that area?
Many thanks,
Dotan
The text was updated successfully, but these errors were encountered: