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
I'm positive anyone would be annoyed by that. Users should be allowed to toggle a flag at the command-line interface to tell ksy-dl to extract all the types into a hierarchical structure of files:
Not only does this make a specification more easier to sift through and use in code, it also becomes modular now:
fromkaitai_local.foodimportfoodfromkaitai_local.food.potato.bun.steak.chicken.cerealimportcerealfromkaitai_local.food.potato.bun.steak.chickenimportchickenfromkaitai_local.food.rice.cornimportcorn# from kaitai_local.food.cabbage import cabbage <- can omit this now instead of importing it
...
ifmycereal.flakes.value==chicken.cook_method.roasted.value:
# not annoyed
For this to work though, I'd have to:
Adjust the imports for each type
Correct the references to subtypes
(possibly more)
The text was updated successfully, but these errors were encountered:
There exist many
ksy
file specifications that have a mess of nested types. It gets ugly real fast:I'm positive anyone would be annoyed by that. Users should be allowed to toggle a flag at the command-line interface to tell
ksy-dl
to extract all the types into a hierarchical structure of files:Not only does this make a specification more easier to sift through and use in code, it also becomes modular now:
For this to work though, I'd have to:
The text was updated successfully, but these errors were encountered: