Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.fibery.com/llms.txt

Use this file to discover all available pages before exploring further.

If this page doesn’t answer your question, please contact us in the support chat.

​
Is there an or operator available in GraphQL?

Indeed there is no or operation. We propose use several queries in this case. 
{
  nullName: findProjects(name: {isNull: true}) {
    id
  }
  emptyName: findProjects(name: {is: ""}) {
    id
  }
}

​
Can a GraphQL “find” query return only the count of records found?

Unfortunately, it is not supported in GraphQL for now. However many things can be done using native Fibery API.

​
Can you provide a GraphQL example that adds multiple selections to a multi-select field?

mutation {
  articles(id: {isNull: false}) {
    linkTags(name: {in: ["One", "Two"]}) {message}
  }
}
Example above for databases, and for enums you can just use update 
mutation {
  articles(id: {isNull: false}) {
    update(multiSelect: {name: {in: ["One", "Two"]}}) {message}
  }
}

​
Does the Fibery GraphQL API support fragments?

No, fragments are not supported in the current version of the Fibery GraphQL API.
We recommend using fully expanded queries instead.
  • Why aren’t fragments supported?
Fragments are a powerful way to make queries more reusable and maintainable. However, Fibery’s GraphQL implementation prioritizes simplicity and stability, and fragment support is currently not on our roadmap.
  • What should I do instead?
If you’re using fragments to avoid repeating fields across queries, you’ll need to manually repeat those fields in each query. While it may add a bit of duplication, this approach is fully compatible with the current API.
  • Will fragment support be added in the future?
At this point, we don’t plan to support fragments. If your use case critically depends on them, feel free to share more details with us — we’re always open to learning how we can improve.