GraphQL typed schema

Created on 3 April 2025, 22 days ago

Problem/Motivation

Now all behaviors are returned as a string, for each behavior there should be a separate type in the schema. This will make it so that number fields are returned as numbers, text fields as strings, etc.

Additionally having behaviors with multiple values breaks the graphql code, this should be caught when creating separate types for each behavior.

Also we only want to have the behaviors enabled by the entity to be able to get queried by the schema. Before it just return null for behaviors that where not enabled, but this isn't ideal for code completion since we only want the behaviors that really are enabled on an entity.

Feature request
Status

Active

Version

2.1

Component

Code

Created by

🇧🇪Belgium cedricl

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024