Georvic Tur

Results 6 comments of Georvic Tur

Hi, @barbieri . I think I'm facing the same issue. When I run this command: ```bash sgqlc-codegen operation my_schema ./operations/dataset.py /home/georvic/repos/datahub/datahub-web-react/src/graphql/dataset.graphql ``` with the following file: https://github.com/datahub-project/datahub/blob/master/datahub-web-react/src/graphql/dataset.graphql I see the...

Hi, @barbieri . Thanks for taking a look. Yes, it also happens with that version: ![imagen](https://github.com/profusion/sgqlc/assets/10814689/1be5eac6-a85a-4ffc-a8dd-1809c1cb0386) For this version, I don't see the get_enter_leave_for_kind function.

If I use the version I tested originally, I do find the function. After placing a print call, I get the following: ![imagen](https://github.com/profusion/sgqlc/assets/10814689/95b45248-4fa1-4676-b888-8f962f3d1bc2) So, the last element before the exception...

In the case of the lineage.graphql code, this is the lineageFields fragment where the error takes place: - https://github.com/datahub-project/datahub/blob/42260fc5d806d57f80c6d9e47c7653b589b3ede9/datahub-web-react/src/graphql/lineage.graphql#L233C10-L233C23 This other fragment called fullLineageResults uses lineageFields - https://github.com/datahub-project/datahub/blob/42260fc5d806d57f80c6d9e47c7653b589b3ede9/datahub-web-react/src/graphql/lineage.graphql#L293 and the...

Added a traceback here: ![imagen](https://github.com/profusion/sgqlc/assets/10814689/f6268039-a791-4ba4-a448-3819a4771ea1) ```console act/src/graphql/lineage.graphql File "/home/georvic/anaconda3/envs/datahub/bin/sgqlc-codegen", line 8, in sys.exit(main()) File "/home/georvic/anaconda3/envs/datahub/lib/python3.7/site-packages/sgqlc/codegen/__init__.py", line 136, in main args.func(args) File "/home/georvic/anaconda3/envs/datahub/lib/python3.7/site-packages/sgqlc/codegen/operation.py", line 1018, in handle_command gen.write() File "/home/georvic/anaconda3/envs/datahub/lib/python3.7/site-packages/sgqlc/codegen/operation.py", line...

**Oh, I noticed that by moving the queries to the top the issue went away.** Is this expected by the sgqlc?