NavigationService serialization feature request

Sep 1, 2014 at 12:17 PM
Since I'm using Prism Converged I'm missing one feature I built into my own NavigationService which I used before. An auto serializing NavigationService which serializes complex types into json and passes it as the argument to next page would be glorius.

I often have to deal with the situation that I need to pass complex types to the next page and now with the Prism framework I have to serialize it by hand (ok not much work with an extension method but why shouldn't the navigation service manage that for me?).

It would be extremely helpful if i would be able to put an object as the argument and define with an 3rd optional parameter if it should be serialized into a json string. And if somebody want to change this behavior he can inject a custom serialization strategy.

What do you think about my idea?