2023-07-20 pathom | Clojure Slack Archive

pathom

caleb.macdonaldblack 2023-07-20T02:26:30.212519Z

@kendall.buchanan https://clojurians.slack.com/archives/C87NB2CFN/p1681378613155539

(defn processor-exception
  [_env err]
  (if (pcr/processor-error? err)
    err
    (let [msg  (str "Graph execution failed: " (ex-message err))
          data (assoc (ex-data err) ::pcr/processor-error? true)]
      (ex-info msg data err))))

(alter-var-root #'pcr/processor-exception (constantly processor-exception))

This is what I do. Exceptions are too large for me as well.

👍 3

🙏 1

danieroux 2023-07-20T10:17:14.902639Z

Design question: Take an attribute like :comments/internal. We have find grained access control that filters the data in with `wrap-map-select-entry` and this is working well. The data is protected. The question is: How do I remove the attribute from :com.wsscode.pathom3.connect.indexes when processing with boundary-interface ? I could build and present different indexes, or we could filter it out at query time. Which one makes more sense, or is there a third choice? The use case would be to present a smaller index with Pathom Viz based on find grained access rights.

lsenjov 2023-07-26T02:13:31.404799Z

I'm very interested in this too, looking to remove some attributes depending on user, but still needing them for the query as a derived field

pithyless 2023-07-20T17:14:43.075929Z

Subscribing to this 🧵 as I've struggled with similar questions. Also @danie - care to expand on how you organize the "internal" attributes? Do you manage a global list of private attributes? Or use some specific namespace/naming strategy to identify which attributes to filter? Or perhaps something else entirely? Looking for some insights or suggestions on what works and doesn't work in your experience.

Clojurians Log v2

pathom