Referencing an enum of an imported spec doesn't work in some languages

[eric-corumdigital]

OS: Windows
KSC: kaitai-struct-compiler 0.9-SNAPSHOT

my_enum.ksy

meta:
  id: my_enum

enums:
  t:
    0: x

my_type.ksy

meta:
  id: my_type
  imports:
    - my_enum

seq:
  - id: my_field
    type: u1
    enum: my_enum::t

>kaitai-struct-compiler -t javascript my_type.ksy
/seq/0: unable to find enum 'my_enum::t', searching from my_type

[GreyCat]

Initial solution seems to be checked in, along with the test that reproduces the problem. Unfortunately, it's still not a solution, as it looks like different languages have some other problems in adoption of such constructs. Only Ruby seems to pass so far.

[generalmimon]

This has been resolved recently. The relevant test is called EnumImportSeq (previously just EnumImport). Check the CI dashboard - this test now passes in all targets except Construct (which doesn't support imports yet; kaitai-io/kaitai_struct_compiler#242 apparently attempts to add it).

The main general problem was that the compiler didn't generate imports for imported enums. This was solved in commit kaitai-io/kaitai_struct_compiler@bb53205, which fixed EnumImportSeq for C++ and Perl. In Python, references to external enums were also incorrect, which was fixed in commit kaitai-io/kaitai_struct_compiler@e4aebb8.