Skip to content

Fix/ignore nil args in nested pagination#394

Merged
zachdaniel merged 4 commits intoash-project:mainfrom
JVMartyns:fix/ignore_nil_args_in_nested_pagination
Jan 8, 2026
Merged

Fix/ignore nil args in nested pagination#394
zachdaniel merged 4 commits intoash-project:mainfrom
JVMartyns:fix/ignore_nil_args_in_nested_pagination

Conversation

@JVMartyns
Copy link
Copy Markdown
Contributor

@JVMartyns JVMartyns commented Jan 7, 2026

Contributor checklist

Leave anything that you believe does not apply unchecked.

  • I accept the AI Policy, or AI was not used in the creation of this PR.
  • Bug fixes include regression tests
  • Chores
  • Documentation changes
  • Features include unit/acceptance tests
  • Refactoring
  • Update dependencies

Resolve: #393

jsw800 and others added 4 commits November 14, 2025 20:46
- Add tracer parameter to Ash.Query.for_read calls in GraphQL resolvers
- Enables proper AppSignal tracing for GraphQL operations
- Works with Scribble.Telemetry.AppsignalAshGraphql for descriptive span names

Closes: AppSignal tracing for GraphQL operations
Add guards in apply_load_arguments: ensure limit/offset are integers,
filter is a map, and sort is a list. Add test to confirm nested queries
do not raise when limit, offset, filter, or sort variables are nil
@zachdaniel zachdaniel merged commit 7604ca6 into ash-project:main Jan 8, 2026
21 of 22 checks passed
@zachdaniel
Copy link
Copy Markdown
Contributor

🚀 Thank you for your contribution! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AshGraphql.Graphql.Resolver.apply_load_arguments/3 accepts nil for limit, offset, filter, and sort, causing runtime errors

4 participants