Differences in accessing ENUM-IDs between Ruby and Java.
I have multiple different types in multiple different KSY-files. One of those types is managing a lot of ENUMs and most of the users of those ENUMs are contained in that type, but not all to not bloat it too much. If other types need access to elements of some external ENUM, I'm currently using `params` to simply forward the IDs of these elements. In most cases the types are so specific, that only very few IDs to forward are enough already. This way I'm actually working around the limitation that [KS can't handle ENUMS in different types](https://github.com/kaitai-io/kaitai_struct/issues/275) yet.

That leads to code like the following:

    params:
      - id:   oms_rec
        type: fmt_rec_oms
      - id:   fmt_oms_dll_prod_code_meh
        type: u4
      - id:   fmt_oms_dll_device_type_heat_cost_allocator
        type: u4

[...]

    instances:
      is_possible_dev:
        value:  |
                (oms_rec.lid.prod_code.to_i     == fmt_oms_dll_prod_code_meh)                   and
                (oms_rec.lid.address.type.to_i  == fmt_oms_dll_device_type_heat_cost_allocator) and
                (oms_rec.lid.address.version    == 0x00)

That leads to working Java, but `ksv` breaks because of the following error message and generated Ruby:

> [...]/fmt_oms_apl_data_tc_date_g_ams_bug_2543.rb:57:in `is_possible_dev': uninitialized constant FmtOmsAplDataTcDateGAmsBug2543::I__FMT_OMS_DLL_PROD_CODE (NameError)

    def is_possible_dev
      return @is_possible_dev unless @is_possible_dev.nil?
      @is_possible_dev =  ((I__FMT_OMS_DLL_PROD_CODE[oms_rec.lid.prod_code] == fmt_oms_dll_prod_code_meh)[...]
      @is_possible_dev
    end

The mentioned constant `I__FMT_OMS_DLL_PROD_CODE` is the reverse mapping of the ENUM I'm interested in and which is contained in the external type `oms_rec`. That type is properly imported in KSY as well, else things wouldn't compile most likely.

    imports:
      - ../../../../../record/oms/fmt_rec_oms

But I don't see any `require`-statements or else in the generated ruby. Things are easy for Java because you model ENUMs as classes there which simply have the attribute `id`, so no need to import anything or cross classes using some static, class-level globals or such. But my KSY seems to be correct in the end, it only doesn't work because of differences in the generated code of target languages.

Any idea how to handle my use case?