Giters
absinthe-graphql
/
absinthe_relay
Absinthe support for the Relay framework
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
180
Watchers:
15
Issues:
87
Forks:
88
absinthe-graphql/absinthe_relay Issues
Consider `Base.url_(de/en)code64` with `padding: false` for Global IDs
Updated
a month ago
Comments count
13
Error with schemas defined via macro with modern payloads
Updated
a month ago
Comments count
2
PageInfo needs to be shareable in GraphQL Federation
Updated
2 months ago
Comments count
1
Issues while upgrading from absinthe_relay from 1.4 to 1.5
Closed
4 months ago
Comments count
1
Absinthe.Resolution.project/1 for child fields
Closed
2 years ago
Comments count
3
changelog
Closed
2 years ago
Comments count
1
New release
Closed
2 years ago
Comments count
3
Include complexity support in connection notation
Closed
2 years ago
Comments count
13
Connection and edge types non_null?
Closed
3 years ago
Comments count
2
Why using offset-based pagination in Connection.from_query?
Closed
3 years ago
Comments count
1
Converting internal ecto foreign key ids to global ids
Closed
3 years ago
Comments count
1
config Absinthe.Relay causes warnings
Updated
3 years ago
Comments count
2
Integration with Dataloader
Updated
3 years ago
Comments count
6
Feature request: use of non-binary id
Closed
3 years ago
Comments count
4
Release new version
Closed
3 years ago
Comments count
2
Warning about ecto dependency after upgrading Elixir to 1.11
Closed
3 years ago
Comments count
1
ParseIDs middleware cannot find schema_node on subsequent `input` field
Updated
3 years ago
Overriding cursor throws warning
Closed
3 years ago
Comments count
2
Node object from interface implementation results in duplicate ID
Updated
4 years ago
Comments count
2
Breaking change in 1.5: Absinthe.Relay.Mutation.Notation.Modern.output/2
Updated
4 years ago
Warning on creating node object
Closed
4 years ago
Comments count
2
Helpers for working with connections
Updated
4 years ago
Absinthe.Relay.Node.ParseIDs causes runtime error if occurs more than once in a mutation query
Updated
4 years ago
Custom Cursor from external endpoint
Updated
4 years ago
Absinthe.Relay.Connection.Options
Closed
4 years ago
Comments count
3
[Absinthe v1.5.0-rc]: Connection default pagination args not configured
Closed
4 years ago
Comments count
7
Usage of ParseIDs Middleware in Subscription
Updated
4 years ago
Comments count
3
Problem with backward pagination using Connection.from_query
Updated
4 years ago
Comments count
7
v1.5.0-alpha.0 doesn't support Ecto 3.0
Closed
4 years ago
Comments count
2
Invalid types are allowed to go through the node field's resolution
Closed
5 years ago
Comments count
12
non-null connections
Closed
5 years ago
Comments count
1
Edge Cursors nullable
Closed
5 years ago
Comments count
1
Benefits of returning a specific error message when ParseIDs fails?
Closed
5 years ago
Comments count
4
Dynamic value enclosing quotes use different characters in some error messages
Updated
5 years ago
Comments count
1
Absinthe.Relay.Connection.from_query may have wrong type
Updated
5 years ago
Connection.from_dataloader/5 helper?
Updated
5 years ago
Comments count
5
Absinthe.Relay.Connection.Notation.connection/2 not defined
Closed
5 years ago
Access information from parent node in custom edge resolver
Updated
6 years ago
Comments count
1
Use with Dataloader?
Closed
6 years ago
Comments count
7
Use connection with subscriptions
Closed
6 years ago
Comments count
1
Issue with schema generation
Closed
6 years ago
Connection offset and limit computation doesn't handle nil correctly
Closed
6 years ago
Comments count
2
Update hasPreviousPage logic to match spec changes
Closed
6 years ago
Comments count
1
issue with has_previous_page
Closed
6 years ago
Comments count
3
Incosistency on Connection.offset/1
Updated
6 years ago
Support for meta when using the payload macro
Closed
7 years ago
Comments count
7
`Could not find schema_node for x` when using ParseIDs in payloads (v1.4, modern)
Closed
7 years ago
Comments count
1
Allow null on ParseIDs
Closed
7 years ago
Comments count
1
node field resolution errors when schema-level middleware puts an error result in
Closed
7 years ago
Comments count
3
Ecto in mix is an older version
Closed
7 years ago
Comments count
1
Previous
Next