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
print functions for the FsHttp representation of Request and Response records are currently implemented in Print.fs, which export Request.print () and Response.print (). Those functions are only used when FsHttp is used in FSI (see FsiInit.fs).
It would be nice (e.g. for debugging purpose or in non-FSI environments) having a ToString() overload per-default in Response and Request that output similar information as when using print(). Since the print function implementation is long, it should not "pollute" the definition of Request and Response (which are defined in Domain.fs) and stay separated from definitions in Domain.fs.
What could be a good way of bringing together
Print functions reside in a separate module
ToString implementation for Response and Request generalls using the ones in Print module
Slightly different ToString / print implementations for non-FSI and FSI, which is: In non-FSI environments, any ToString() implementation should not cause side effects (e.g. like reading from Request/Response streams).
?
The text was updated successfully, but these errors were encountered:
print
functions for the FsHttp representation ofRequest
andResponse
records are currently implemented inPrint.fs
, which exportRequest.print ()
andResponse.print ()
. Those functions are only used when FsHttp is used in FSI (seeFsiInit.fs
).It would be nice (e.g. for debugging purpose or in non-FSI environments) having a
ToString()
overload per-default inResponse
andRequest
that output similar information as when usingprint()
. Since the print function implementation is long, it should not "pollute" the definition ofRequest
andResponse
(which are defined inDomain.fs
) and stay separated from definitions inDomain.fs
.What could be a good way of bringing together
ToString()
implementation should not cause side effects (e.g. like reading from Request/Response streams).?
The text was updated successfully, but these errors were encountered: