Add monocle-ts Optional about remote-data-ts

[sutarmin]

hey, @anthonyjoeseph , thanks for your thoughts! No doubts it's a nice thing to have such helper utilities, but I agree with @raveclassic here that this is not related to core RemoteData logic and should be placed in some external library/end code.

[raveclassic]

Thanks for suggestion and sorry for such long answer. Unfortunately I don't think it's a good idea to add monocle-ts to dependencies. Yeah I'm ok with io-ts because it is related to the data structure (serialization/deserialization). But I don't see any relation to optics especially if the suggested function is trivial.

[anthonyjoeseph]

I think this addition would be appropriate, since RemoteData is an ADT, and ADTs are related to optics

I think adding optics support helps uphold the isomorphism between RemoteData<E, A> and Option<Option<Either<E, A>>>

However, I understand the maintenance hassles of added dependencies, and that it is ultimately a judgement call

[anthonyjoeseph]

I understand that. Any thoughts about what such an external library might look like? Maybe something similar to io-ts-extras? It seems too specific for fp-ts-contrib.

Maybe we need a monocle-ts-contrib. Does something like this exist already?

Forgive me, I don't mean for this thread to become too off topic, this just seems to me like a potentially common use case (deeply nested remote data could go inside redux state, etc) and I'm not sure where's best to post this

[anthonyjoeseph]

FWIW both the Elm and Purescript versions of RemoteData include optics (and the Elm interface even avoids a dependency)