pathom3
pathom3 copied to clipboard
wilkerlucio
A library for navigating data.
It looks like `::p.gql/root-entries-map` entrypoints do not get re-used for all attributes in the request. My expectation is that if a request contains all of the attributes necessary for a...
I was wondering if Pathom 3 supports live subscriptions. I have a [Manifold Stream](https://aleph.io/manifold/streams.html) that receives updates at around 0.25s. I'd love to expose an API that allows users to...
Seems like those attributes conflict for the same purpose, must be checked and if it's the case, remove one of them, otherwise get docs explaining the distinction.
When a resolver throws an error, it must not cache that error value. As of now, it does cache that error value, and in case it's a persistent cache you...
In the new strict mode, an attribute failure may happen because: 1. Attribute is unknown in the index 2. Attribute exists in the index, but available data isn't enough to...
Allow a user query to extend a nested input from a resolver. In the following example scenario: ```clojure (pco/defresolver all-people3 [{:swapi.Root/keys [allPeople]}] {::pco/input [{:swapi.Root/allPeople [{:swapi.PeopleConnection/people [:swapi.types/Person]}]}] ::pco/output [{:swapi/all-people [:swapi.types/Person]}]} {:swapi/all-people...
Currently, in the case of lenient mode, errors are not propagated back. Need to explore combinations of lenient vs non-lenient parsers connecting and see how the errors should propagate.
I find it quite hard to explain but I managed to reproduce this bug in small repro: ```clojure (ns avisi-apps.pathom-bug (:require [com.wsscode.pathom3.connect.operation :as pco] [com.wsscode.pathom3.connect.indexes :as pci] [com.wsscode.pathom3.interface.async.eql :as p.a.eql]...
## Problem Analysis ### Description When a client makes a request invoking the same mutation multiple times, Pathom only returns the last response. Example: ```clojure (pco/defmutation add-node [{:keys [id]}] (println...
(See [Slack Discussion](https://clojurians.slack.com/archives/C87NB2CFN/p1692025696580489?thread_ts=1692007239.025389&cid=C87NB2CFN) for further reference) Resolvers with higher specificity should get priority over resolvers with less specificity. Specificity can be determined by the number of input attributes. ## Problem...
