fetch
fetch copied to clipboard
Simple & Efficient data access for Scala and Scala.js
1. I don't see how this passes, my quick arbitraries must not be good enough. 2. product/traverse batching seems like it has to be cheating somehow the monad laws 3....
Updates * [org.scalameta:mdoc](https://github.com/scalameta/mdoc) * [org.scalameta:sbt-mdoc](https://github.com/scalameta/mdoc) from 2.2.24 to 2.3.1. [GitHub Release Notes](https://github.com/scalameta/mdoc/releases/tag/v2.3.1) - [Version Diff](https://github.com/scalameta/mdoc/compare/v2.2.24...v2.3.1) I'll automatically update this PR to resolve conflicts as long as you don't change it...
Hi everyone. I am having troubles using this trait: ```scala trait DataCache[F[_]] { def lookup[I, A](i: I, data: Data[I, A]): F[Option[A]] def insert[I, A](i: I, v: A, data: Data[I, A]):...
We can define timeout on entire Fetch after run with cats effect, but I can't find how to define timeout on 'sub' Fetch and handle it with 'default' value. Something...
which fails the ci
Currently the methods that fetch data in `DataSource` require an effect type `F` with `Par[F]` and `ConcurrentEffect[F]`. `Par` is required due to the `DataSource#batch` implementation defaulting to running individual fetches...
From the gitter channel: >I like the deduplication feature, but when I run a fetch I'd like to be able to get the data as it becomes available. (Imagine I...
Cacheing resource request is a great feature. However, I was wondering if it would be nice to support cache backends such as Redis or MemCached.
Currently, `DataSource#fetch` looks like this: ``` scala trait DataSource[Identity, Result] { def fetch(ids: NonEmptyList[Identity]): Query[Map[Identity, Result]] } ``` The `fetch` method of a data source just receives a non empty...