Unlike the include-objs flag which forces sszgen to only generate objects that are included, the exclude-objs flag performs that filter after the generation is done. Thus, if an invalid object is present on the file, it cannot be excluded and the generation fails like in #75. An example of an invalid type would be:
type Bytes []byte
Since we cannot add tags to this alias struct. This type could never be rendered.
I am still not sure if we should be smart and skip right away these objects from the generation. Then, for now, this is a good enough workaround to remove this limitation.
It also fixes the core issue on #75 in which the tags used to declare one alias would be used in another one.
Unlike the
include-objsflag which forcessszgento only generate objects that are included, theexclude-objsflag performs that filter after the generation is done. Thus, if an invalid object is present on the file, it cannot be excluded and the generation fails like in #75. An example of an invalid type would be:Since we cannot add tags to this
aliasstruct. This type could never be rendered. I am still not sure if we should be smart and skip right away these objects from the generation. Then, for now, this is a good enough workaround to remove this limitation.It also fixes the core issue on #75 in which the tags used to declare one
aliaswould be used in another one.