2.0 Breaking Changes Checklist

Open
#343 0 comments 0 reactions 1 assignee View on GitHub

@olirice is already working on this.

Since Mar 22, 2023.

Assessment

This issue has not been assessed yet.

Description

A list of breaking changes to enforce when moving to 2.0

  • (maybe) Disable comment directives defining relationships in favor of explicit SQL functions
  • (WIP) Remove the requirement for function-based computed columns to start with _ and remove the prefix stripping logic
  • remove nin, neq and any other "negated" filter that can be better expressed using not composition in filters
  • (maybe) rename graphql.resolve to graphql.graphql so publicly exposing the function gives it a reasonable name
  • re-order inputs to graphql.resolve so it matches GraphQL over http expectations without graphql_public.graphql
  • non-null foreign keys might still be nullable relations if RLS is active ref
Dominant language
Rust
Stars
3.4k
Forks
141
Avg merge
19m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/pg_graphql

All issues in supabase/pg_graphql

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.