cc @ronger4

I will investigate further and see if other properties differ in type.
Just to understand,
In the example case you mentioned I should convert TimeSpan to be DateTime object, right?
So, the user will expect the output to be the same as the input that he entered.

I think it’s still a timespan but I could be wrong but yes the input format of the attributes should align with output value from the _info module.

I investigated further.
Every time attribute representation will differ from the input.
The native IIS is working with timespan hence it only accepts TimeSpan formatting when setting the attribute (trying to set it as dict represented TimeSpan - will fail and it has no property of such)
For example:

"msg": "Failed to clear attribute to Web App Pool TestPool. Attribute: processModel.pingResponseTime.Seconds, Exception: Property processModel.pingResponseTime.Seconds does not exist at path \\\\WIN-Q36ISGBPHBD\\AppPools\\TestPool."
}

The reason that the output in the end is a dictionary formatted timespan and not string format is most probably due to the fact
that during the JSON serialization process in the module, the TimeSpan object is automatically decomposed into a dictionary of its properties. This happens without any explicit conversion logic in the module.

If we want to align it to be a string too, I can convert it manually to string during the handling in the module itself.
It might be the right way since the default representation when trying to fetch from PowerShell terminal is string representation too.

 (Get-Item -LiteralPath IIS:\AppPools\testron).recycling.periodicRestart


memory         : 0
privateMemory  : 0
requests       : 0
time           : 1.05:00:00

The advantage of the way of how it is handled now is that the output is more readable with the dictionary representation.