For the reasons see https://github.com/building-envelope-data/api/blob/f75edaac57e325092effceca10177ae11d2c3164/apis/database.graphql#L1-L10 and https://github.com/building-envelope-data/api/blob/f75edaac57e325092effceca10177ae11d2c3164/apis/database.graphql#L417-L440 Currently, it encodes only the UUID (together with the table name to be unique in the database), see
|
descriptor |
|
.ImplementsNode() |
|
.IdField(t => t.Id) |
|
.ResolveNode((context, id) => |
|
context |
|
.DataLoader<TEntityByIdDataLoader>() |
|
.LoadAsync(id, context.RequestAborted)! // Notice the null-forgiving operator `!`. It's bad that we need to use it here. |
|
); |
, and thus violates field stability. The same is true for the metabase project.
For the reasons see https://github.com/building-envelope-data/api/blob/f75edaac57e325092effceca10177ae11d2c3164/apis/database.graphql#L1-L10 and https://github.com/building-envelope-data/api/blob/f75edaac57e325092effceca10177ae11d2c3164/apis/database.graphql#L417-L440 Currently, it encodes only the UUID (together with the table name to be unique in the database), see
database/backend/src/GraphQl/Entities/EntityType.cs
Lines 17 to 24 in d45f78d