74 results found
-
Support inline/embeded types stored as structured JSONB columns
Allow storing structured types in JSONB columns using an @inline (or @embed) directive on the field.
type Address {
street: String!
street2: String
city: String!
state: String!
zipcode: String!
}type User @table {
address: Address @inline # stores as JSONB
}19 votes -
1 vote
-
File Uploads
Store and retrieve large files with Data Connect through an integration with Google Cloud Storage.
25 votes -
Generated SDK types
Given a schema with a nullable type
type MyType @table() {
id: uuid!
nullableString: String
}When running a query that selects records from MyType and filters out null values for nullableString, the generated SDK still types nullableString as string | null (or string? | null). Even though the query ensures no null values are returned for that field.
It would be great if the SDK could be smarter and refine the generated type to just string when the query explicitly filters out null values for that field.
1 vote -
Enhanced Foreign Key Behavior
I am reaching out to share a suggestion regarding the current implementation of foreign key constraints in Firebase DataConnect.
Currently, it appears that the default behavior for foreign keys is automatically assigned during schema deployment, and there is no way to explicitly define ON DELETE and ON UPDATE rules (e.g., NO ACTION, CASCADE) in the GraphQL schema. This limitation has the following implications:
1. Deployment Overrides: Even if these rules are manually adjusted in the underlying PostgreSQL database, deploying an updated schema resets the rules to the platform’s defaults.
2. Lack of Customization in Schema: Adding support for directives like…5 votes -
Automatic GraphQL schema from existing SQL schema
When onboarding an existing postgres database, Data Connect can read the postgres schema and attempt to generate a corresponding GraphQL schema. Users with existing databases can immediately benefit from Data Connect client SDKs, query based auth, and connector connection pooling without manually writing GraphQL that matches their database schema.
2 votes -
Extension support, i.e. postgis
One of the things that makes postgres great is it's extension support. Inability to integrate with extensions like postgis is a severe blocker.
20 votes -
GraphQL Federation
Support federating a Data Connect service with other GraphQL schemas using federation protocols. Stitch together existing GraphQL services with Data Connect.
18 votes -
Interfaces, Union types in GraphQL
Support for GraphQL Interfaces or Union Types through the built in GraphQL schema builder tool. This was extensively discussed in the Google Chat group.
14 votes -
Managed SQL Schema Migrations
Data Connect automatically queues and applies database schema migrations as you make changes to your application's schema including destructive migration detection and diff approval.
18 votes -
Connect to an existing instance of another project
Allow connections to PostgresSQL instances in other projects using Shared VPC, etc.
14 votes -
1 vote
-
Support storing unstructured json in Postgres jsonb column
Postgres support jsonb column that can store arbitrary jsonb objects, very suitable to store unstructured / semi-structured API output.
Postgres also supports index on fields within jsonb.
Can data connect support jsonb column? Mapping fields of API object to Postgres columns can be a headache
14 votes -
@unique argument to use UNIQUE NULLS NOT DISTINCT
Add an argument to the @unique annotation that allows users to choose between using PostgreSQL's "UNIQUE NULLS NOT DISTINCT" constraint or the standard "UNIQUE" constraint when defining a unique constraint.
2 votes -
Configure Firebase Lambda and API endpoint exposure
Automate the "subprocesses" to open up an endpoint to interact with Firebase Lambdas, which have the access permissions to make changes to the realtime database, storage, and auth core functionality. This encompasses many applications' backend use cases if interactive via REST API. So open these lambdas to access services via HTTP calls.
1 vote -
Documenting Schema and Connections
One of the things that was important to me when developing clients in Apollo graphql is the playground.
You should be able to create a document with a proper description.
And currently, description using “”” is only possible for schema type. It is also needed for query, mutation.
And we need to be able to generate them with the SDK and then see them in the client code.3 votes -
have a unity sdk for dataconnect
I'd like a Unity SDK for DataConnect
3 votes -
Postgres Functions exposed as an API
Similar services, like postgraphile, allow exposing queries / mutations as postgres functions. It's extremely powerful, and allow extremely custom queries / logic for exposing data to the clients.
13 votes -
Add service to Data Connect Triggers
Trigger a Cloud Function that will add the service and schema to Data Connect when the user signs up successfully.
3 votes -
Web SDK generation to also export schema types
Currently the dataconnect:sdk:generate command in firebase-tools will generate functions for queries and mutations. There are cases where having TypeScript interface reflections of the schema types would also be beneficial.
AFAIK there's no existing tooling that will conveniently do this mapping (due missing types that one can find in .dataconnect/schema/prelude.gql when the emulator is running).
2 votes
- Don't see your idea?