thus we only request the items we need
btw:
The items endpoint, does not have an ids=all parameter
so we need to do it different
but it'd make querying easier for a
FindAll()
that's the easiest way
Actually, if the request is not a single item request I'm only using paging right now
Converters did change a bit, I'm experimenting a bit still, but I'm trying to make the converters type safe, but non generic so we can pass them around easier.
The goal is, that you only need to pass only the necessary converters, and not do stuff like pass the whole batch converters etc.
Higher order is a wunderful thing :P
The goal is, that you only need to pass only the necessary converters, and not do stuff like pass the whole batch converters etc.
Higher order is a wunderful thing :P
so I won't be completely clueless when we make that switch
OH happy new year by the way
it's not even funny
Also I'm currently refactoring the repositories to use HTTPClient and the new repository layout. Converters will stay the same for now. After those chances work fine we can tackle the converters itself
I'm also thinking of a very basic and small InMemory cache
well
what you said about ITimeSensitive
where the margin is set by a response header
which is the server time when the response was generated
who knows what they changed this time :(
Oh boy, was it
DateTime or DateTimeOffset? The latter, right?
DateTime is used to represent a moment