You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
( project_id, scene_id ) → scene . ( project_id, id ).
I also have a FK of project_id → project . id
After adding the Hasura relationships, in the permission builder for scene_resource, I can select project no problem, but if I select either scene or resource, the console throws the error.
What is the expected behaviour?
That it doesn't throw an error and I can build a permission through the console...
Version Information
Server Version: v2.42.0 (tested on 2.40 as well)
CLI Version (for CLI related issue): v2.42.0
Environment
All
What is the current behaviour?
When using a composite foreign key, the permission builder throws an error: TypeError: Cannot read properties of null (reading 'schema')
For example, I have the tables:
project
,scene
,resource
, andscene_resource
.scene
andresource
both reference project with a FK.scene_resource
references all the tables.scene_resource
I have composite FKs of:After adding the Hasura relationships, in the permission builder for
scene_resource
, I can selectproject
no problem, but if I select eitherscene
orresource
, the console throws the error.What is the expected behaviour?
That it doesn't throw an error and I can build a permission through the console...
How to reproduce the issue?
https://github.com/nyoung697/hasura-bug
Screenshots or Screencast
Screen.Recording.2024-10-26.at.9.32.43.AM.mov
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
I am able to create the permissions by manually modifying the .yaml file directly, then calling
hasura deploy
Keywords
hasura console, TypeError: Cannot read properties of null (reading 'schema'), composite keys
The text was updated successfully, but these errors were encountered: