Realm

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 24 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  2. Pagination in GraphQL

    We have slicing via limit: INT, but we do not have the ability to specify an offset. Are there plans to add this soon?
    GraphQL Documentation actually specifies their pagination terms as follows:
    first: int
    offset: int
    after: _id
    Are there plans to implement this at all?

    11 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow deeper relationships under Rules

    I really like being able to use GraphQL and how you can auto generate a schema but when trying to relate fields I noticed it would only let me relate top level fields.

    For example - we have "accounts" and "users" under accounts with user Id on a related object. But I cannot do related userId back to account.user.userid since user is an object. I was hoping after I generated a schema for all the collection I would be able to drill down deeper but no such luck.

    7 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  4. Single schema of truth: JSON Schema / Realm Schema / GraphQL Schema / TypeScript Types

    I think the current recommended initial prototyping workflow for a Realm web SDK user is like this:

    1) Add first data in collection (manually, on Compass etc.)
    2) Generate JSON Schema (manually click a button on web UI)
    3) Set up relationship (manually, on web UI)
    4) Download GraphQL Schema (manually click a button on web UI)
    5) Get TypeScript types and React hooks (automatically generated by graphql-codegen CLI)
    6) If you use another Realm SDK somewhere else (ex. Node.js sdk for server side), write Realm Schema (manually)

    This is not very developer friendly, and requires back-and-forth work between CLI,…

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  5. Adding or removing elements from array fields

    It would be helpful to support array add/remove in update mutations. I've been running into this most often when dealing with one-to-many relationships.

    For example, adding/removing books from an author. Currently, you would have to fetch the entire array of books to add or remove the book linked to the author. If I could supply the foreign key to add/remove from the relationship that would be fantastic.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  6. Custom GraphQL Schema for MongoDB Realm

    Dear MongoDb GraphQl Stitch developers,

    Is it possible to add an ability to modify the final GraphQl schema (in order to remove unnecessary for my API stuff)
    OR
    Build it based on existed roles?

    For example, Im building a "read only" GraphQl API and have NO roles that can actually modify the data. So I find it illogically to have mutations in the Final GraphQl schema.

    It would be great to have an ability to choose which exactly mutations/queries I need for my GraphQl.

    Thank you.

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support for updating nested fields in GraphQL mutations

    I want to do the equivalent of {$set: {"details.pm_stage": "...."}}

    export const UPDATEPROJECTDETAILS = gql`

    mutation UpdateProjectDetails($query: PsprojectQueryInput!, $pmStage: String!) {
    
    updateOnePsproject(query: $query, set: {details: {pm_stage: $pmStage}}) {
    _id
    }
    }

    `;

    right now the whole "details" subdocument gets overridden

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  8. Special variables and values

    For example, I have a field called UpdatedAt which is a datetime field, I'd like to have it set to the system datetime of the server. If I use trigger to update the value of this field, then I will not be able to read the value right after the mutation completed. So I want to do something like ' Field: SYSTEMDATETIME', then the server side of GQL will translate SYSTEMDATETIME to the correct value.

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm GraphQL  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base