Comments (2)
Hello, this is a complete list of all the namespaces you might use, but usually, you only need a few of them. The problem with an API namespace is that it will end up requiring many things you don't need, adding to start time. This was a problem in Pathom 2 and that's the reason to get things separate in Pathom 3.
In reality, you can do a lot with just 3 of those:
; this one to create resolvers and mutations
[com.wsscode.pathom3.connect.operation :as pco]
; this one is to register resolvers, creating the indexes
[com.wsscode.pathom3.connect.indexes :as pci]
; then to setup EQL processor you will use:
[com.wsscode.pathom3.interface.eql :as p.eql]
; OR, in case you use async, gonna be this instead:
[com.wsscode.pathom3.interface.async.eql :as p.a.eql]
These will cover most of the standard Pathom operations, in projects that are more than demos, usually, you gonna use pco
in a lot of places to define resolvers, while the indexes and operation you will have in a single place to start the register and set up the EQL processor.
You are welcome to set up your own API namespace as well if you like to concentrate the things in a single namespace. So I don't consider this an issue at the library level.
from pathom3.
Maybe some spec style "dynaload" would help with the start time. Alternating between unfamiliar namespaces while learning a new library is annoying and adds unnecessary overhead. I'll be waiting for a better experience.
from pathom3.
Related Issues (20)
- p.eql silently drops nested attributes HOT 2
- StackOverflowException when using foreign register.
- Error message refers to clojure.core/name instead of the resolver op-name
- Ensure plans are cached independent of a query's idents' values
- Remove placeholder param data feature from core features HOT 1
- Plugin `mutation-resolve-params`, error path handling
- Errors with missing attributes in lenient-mode / batch resolvers
- Dynamic resolvers are called more than necessary.
- :batch? true sometimes makes parts of query unresolvable
- process-one returns nil instead of false
- Resolvers are not run in parallel with other resolvers HOT 3
- Single resolvers are running at the same time as a bulk resolver. HOT 1
- [bug] If a bulk resolver returns a list of length <> input length pahtom hangs
- Implicit resolver priority based on number of input attributes HOT 1
- Top-level invocation of resolver in a `def` throws
- Nested input lists are reversed
- How to model and resolve optional heavy attributes HOT 1
- Idents don't run in parallel
- Different `pco/params` behavior in Clojure vs. ClojureScript
- The plural of `index` is `indices`, not `indexes` HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pathom3.